While looking through the fink codebase in CVS, I noticed that we
still use a separate ChangeLog for each directory. To be frank, I do
not know why we ever made this separation (it simply existed from day
one), but now that I have some distance from the code (not having
worked on it for a very long time), I wonder if this is a good idea...
Most other projects I know have a single ChangeLog in a central
place. The advantage is that you only have one place to search if you
are looking for a specific change. Also, if you want to know what
changed since your last cvs up, you only have to look through one
ChangeLog. And if you commit a patch that affects multiple
directories at once, you only add one ChangeLog entry, instead of
multiple (which makes sense if those changes really belong together;
they might not even make sense when viewed separately).
Hence, I am wondering whether we should merge all those ChangeLogs
(21) and only keep a single one... This would involved changing
entries like
2001-05-08 Christoph Pfisterer <[EMAIL PROTECTED]>
* config.guess, config.sub: Updated with latest version
(2001-04-20) from ftp.gnu.org.
such that they list the full file path, i.e. "update/config.guess,
update/config.sub" in this case. And of course removing duplicate
entries etc., in short, a lot of manual work.
Clearly, this would be a *lot* of work for perlmod/Fink/ChangeLog
which is by far the biggest. All the others are fairly short. My
suggestion hence would be to start out by merging all ChangeLogs
*except* for perlmod/Fink/ChangeLog into a single one (this should be
relatively quickly done, and I would do it). While not quite
"perfect", this would mean that at least there are only two, instead
of 21, ChangeLog files to watch & update. Merging "perlmod/Fink/
ChangeLog" then could be done at a later point, or gradually, or with
a clever script, or by hiring some slaves, or so ;-).
What do you think? Is this idea bogus?
Cheers,
Max
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fink-devel
