|--==> "VS" == Ville Skytt <Ville> writes: VS> How about this; VS> When there are new releases of packages, there would also be an entry in VS> the package ChangeLog(s) like VS> 2002-03-06 John Doe <john.doe(a)xemacs.org&gt; VS> * Makefile (VERSION): Updated to x.xx. VS> This would make it easier for people not involved in XEmacs development VS> to see changes between releases (before|when|after) installing them. I'll think about doing this. But only if... VS> I think this could be automated pretty easily too. You can come up with a way to do this. :-) -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|

|--==> "VS" == Ville Skytt <Ville> writes: VS> On Fri, 2002-03-08 at 02:06, Steve Youngs wrote: VS> I think this could be automated pretty easily too. VS> Well, actually I misspelled "semi-automated" :) VS> As I'm not familiar with the current process of how new package releases VS> are done, I'll assume that you manually update Makefile (VERSION) and do VS> a "make bindist". More or less, yes. VS> There could be a M-x foo-bar-update-package-version somewhere which VS> would prompt for a package name, then the new version (defaulting to VS> VERSION + 0.01). It would update Makefile (VERSION) and do a VS> add-change-log-entry with a proper message. Useful? Hmm. Shouldn't be too hard to hack something together. I'll look into it. -- |---<Steve Youngs>---------------<GnuPG KeyID: 10D5C9C5>---| | XEmacs - It's not just an editor. | | It's a way of life. | |------------------------------------&lt;youngs(a)xemacs.org&gt;---|