It seems to me that the changelogs aren't being properly updated when the SVN is altered. I started an SVN build of x86_64 multilib CLFS yesterday and it was using bash 3.1. I think that it was SVN-20061010, but I'm not sure. Either way, it was the most recent. Today, when I continue dbuilding CLFS, it was now SVN-20061011. The changelog says NOTHING about what was changed. If that's the case, personally I would assume that it was only typos and the like that was changed - nothing big. However, when I got to bash, it was now version 3.2. I would have thought that that would be a big enough change to get into the changelog, but apparently not. I don't know what exactly is supposed to end up in the changelog, but I would appreciate it if at minimum all the package version changes that are made would make it into the changelog. Certainly when we get a new version of the SVN and there's nothing in the changelog stating why, I have to wonder what was changed and if it's going to affect any builds that I'm currently doing that follow the SVN. I appreciate all the hard work that the development team is putting in on CLFS, but I'd appreciate it if the changelog was maintained better. Thank you.
- Jonathan Davis _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
