-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 02.12.2013 05:48, schrieb NeilBrown:
So does that mean we need to create e2fsprogs-mini?? Is it sufficient just to create an e2fsprogs-mini.spec file in the e2fsprogs package, or do we need a separate e2fsprog-mini package, just like there is a separate krb5-mini package? As long as pam can live without libtirpc, there is no need for such drastic measures. removing useless doxygen is great and building against krb5-mini is great too - splitting more packages without need is too expensive.
To update krb5 to exclude doxygen from the -mini build I presumably need to submit updates to both "krb5" and "krb5-mini" - is that correct?
krb5-mini is a 2nd spec file in krb5, you only need to submit krb5. Greetings, Stephan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlKcJYgACgkQwFSBhlBjoJYzBACgmpkH7rYRX80BvnOruoarLvx2 THkAoLGXT69H0ndGoTqSWaeptrDzd55D =2wpY -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org