[yast-devel] Truncating changes file
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? Thx && Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
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: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Arvin Schnell napsal(a):
On Tue, Apr 01, 2008 at 05:50:35PM +0200, Lukas Ocilka wrote:
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.
Hmm, you're right, it seems to cut something off: `LANG=C rpm -q -changelog yast2-installation | tail -n6` * Mon Jul 10 2006 mvidner@suse.cz - When running Novell Customer Center Configuration the second time, do not add duplicate update sources for graphic card drivers (#188572). - 2.13.134 But it's still quite a lot left there: `LANG=C rpm -q -changelog yast2-installation | wc -l` 1358 In my opinion, we should know what to drop and what to leave... Lukas
Am Dienstag, 1. April 2008 schrieb Lukas Ocilka:
But it's still quite a lot left there:
`LANG=C rpm -q -changelog yast2-installation | wc -l` 1358 But still only 51K :)
BTW: what's really bad is that the changelog is in the rpm _uncompressed_. But it's just medium size - the installation is done by tar now ;-)
In my opinion, we should know what to drop and what to leave...
Actually it's a requirement that we keep the changes since our last enterprise version - after Code11 we can drop it dramatically for a while :) Greetings, Stephan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Arvin Schnell -
Lukas Ocilka -
Stephan Kulow