On Tue, Apr 01, 2008 at 05:50:35PM +0200, Lukas Ocilka wrote: > Hi, > > I've just sent new yast2-installation into autobuild and one thing made > me stop to think about our changes files: > > yast2-installation-2.16.28.tar.bz2 size: 225750 > yast2-installation.changes size: 213761 > > Is it really wort having 208 kB of changes for such package? Is anybody > interested in it? In my opinion, users are interested in the changes > that have been made since the last release or codebase change. Ancient > changes are just filling-up the RPM database, that's all. > > My proposal is to keep the changes file untouched but change the > `make package` script to cut off > a.) changes that belong to some older release (e.g., 10.2 vs 10.3) > b.) changes that belong to some older codebase (e.g., 10.3 vs 11.0) > > We can simply use the package VERSION which should be increased by one > with every release (currently 2.16, next will be 2.17). > > This would make our installation smaller, RPM faster and we would still > keep our changes in SVN. The build service checks would have to be > changed probably because they check for inconsistencies in changes files > too. > > What do you think of that? > Any better idea?
Doesn't autobuild strip the changes file while building RPMs? If not, it should go there so that every packages profits from it. ciao Arvin -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
