Re: Bug in cperl-mode.el - unexpanded CVS keyword
On Thu, Dec 22, 2011 at 2:04 AM, Stephen J. Turnbull wrote:
Vin Shelton writes:
> there are many occurrences of CVS keywords in the package sources
> and not all of them are in comments. What should we do about this?
Seems to me that usage is likely to vary and we should just deal with
them case-by-case.
In this case if our cperl-mode is quite close to Ilya's version 6.2,
just changing to 6.2 as you suggest seems best. But if it's been
heavily modified, maybe Ilya doesn't want that (Ilya has not been
famous for volunteering to help fix bugs in code that isn't his...).
So you see the problem with trying to have a blanket policy, at least
without substantial thought about it.
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.) If
so, I'll download the pre-built packages and extract the current
values of '$Revision$' and update the affected packages. Manually
updating those keywords will " 'ardly hever 'appen " (to coin a
phrase).
Mercurial can do keyword expansion (see
http://mercurial.selenic.com/wiki/KeywordExtension if you're
interested), but the revision strings are things like "2ad3dcb8d811",
likely not what the original author intended.
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.
- Vin
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta