[opensuse-packaging] derived packages, e.g. openldap2-client
HI! Could someone enlighten me why some packages are derived from others? Example: https://build.opensuse.org/package/show/network:ldap/openldap2 This already generates several different RPMs. Derived from openldap2: https://build.opensuse.org/package/show/network:ldap/openldap2-client Both packages almost use the same .spec files and generate several RPMs. Why does openldap2 not simply generate additional client RPMs? Even the OpenLDAP server uses the client libs anyway. Ciao, Michael.
On Sun, 16 Aug 2015, Michael Ströder wrote:
HI!
Could someone enlighten me why some packages are derived from others?
Example:
https://build.opensuse.org/package/show/network:ldap/openldap2
This already generates several different RPMs.
Derived from openldap2:
https://build.opensuse.org/package/show/network:ldap/openldap2-client
Both packages almost use the same .spec files and generate several RPMs. Why does openldap2 not simply generate additional client RPMs? Even the OpenLDAP server uses the client libs anyway.
Because of the extra build dependencies of the openldap2-client packages. This enlarges the minimal set of packages to bootstrap for no good reason. Richard.
Ciao, Michael.
--
Richard Biener
Richard Biener wrote:
On Sun, 16 Aug 2015, Michael Ströder wrote:
HI!
Could someone enlighten me why some packages are derived from others?
Example:
https://build.opensuse.org/package/show/network:ldap/openldap2
This already generates several different RPMs.
Derived from openldap2:
https://build.opensuse.org/package/show/network:ldap/openldap2-client
Both packages almost use the same .spec files and generate several RPMs. Why does openldap2 not simply generate additional client RPMs? Even the OpenLDAP server uses the client libs anyway.
Because of the extra build dependencies of the openldap2-client packages.
Sorry, I don't understand your wording. Is the splitting good or bad?
This enlarges the minimal set of packages to bootstrap for no good reason. ^^^^ This sounds ambigous.
Did you rather mean this: Having one package generating also the client RPMs would introduce extra build dependencies to produce the openldap2-client RPMs during bootstrap. Ciao, Michael.
On Mon, 17 Aug 2015, Michael Ströder wrote:
Richard Biener wrote:
On Sun, 16 Aug 2015, Michael Ströder wrote:
HI!
Could someone enlighten me why some packages are derived from others?
Example:
https://build.opensuse.org/package/show/network:ldap/openldap2
This already generates several different RPMs.
Derived from openldap2:
https://build.opensuse.org/package/show/network:ldap/openldap2-client
Both packages almost use the same .spec files and generate several RPMs. Why does openldap2 not simply generate additional client RPMs? Even the OpenLDAP server uses the client libs anyway.
Because of the extra build dependencies of the openldap2-client packages.
Sorry, I don't understand your wording. Is the splitting good or bad?
This enlarges the minimal set of packages to bootstrap for no good reason. ^^^^ This sounds ambigous.
Did you rather mean this:
Having one package generating also the client RPMs would introduce extra build dependencies to produce the openldap2-client RPMs during bootstrap.
Yes.
Richard.
--
Richard Biener
participants (2)
-
Michael Ströder -
Richard Biener