Re: Bug in cperl-mode.el - unexpanded CVS keyword
Vin Shelton writes:
Does that mean you're in favor of manually expanding the
keywords
where appropriate and leaving them fossilized in amber? (I'd guess
that "where appropriate" means wherever they are used in code.)
Since you're proposing to do the work, sure. :-) As I wrote to Mats I
suspect there may be some VCS fallout if there are upstreams still
using CVS, but I'll be happy to help deal with it "if and when".
Mercurial can do keyword expansion, but the revision strings are
things [...] likely not what the original author intended.
Right, and I think cperl's version extractor regexp would blow up on
that, no?
IMO, at some point soon, all the packages need to be re-released
just
so we can build from the latest sources and track down problems like
this.
"Latest sources" means ours, or upstream? I'm not sure I see the
benefit from this.
Certainly it would be good for our image and our own morale if both
packages and core (mea maxima culpa) got on to regular release
schedules, but I don't see the benefit from a one-off effort to
re-release right now?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta