[opensuse-buildservice] Mixing package versions ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have built a package for lifeograph version 0.4.1 in my home project (home:PVince81). The most recent version of this software, which is 0.5.4, only builds in openSUSE factory because it requires a higher version of gtkmm. For the other openSUSE versions like 11.1, only the version 0.4.1 can compile. My question here is whether it is allowed, by convention, to mix such package versions ? It means I would have to modify the spec file to detect which openSUSE version we're building against, and switch the version field accordingly. It also means that both versions of the sources of lifeograph will be present in the OBS package and would also be packed together into the same SRC RPM. Is that correct ? Thanks, Vincent Petry -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkqzvgAACgkQSSdxpfEEQExsLQCgq7hhZRgPw0swl12CuYO+37ng N3sAoJV0M+mO/p/rphC9cEEW1iTfWKal =fYcs -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Freitag, 18. September 2009 19:06:08 schrieb Vincent Petry:
Hi,
I have built a package for lifeograph version 0.4.1 in my home project (home:PVince81). The most recent version of this software, which is 0.5.4, only builds in openSUSE factory because it requires a higher version of gtkmm. For the other openSUSE versions like 11.1, only the version 0.4.1 can compile.
My question here is whether it is allowed, by convention, to mix such package versions ? It means I would have to modify the spec file to detect which openSUSE version we're building against, and switch the version field accordingly. It also means that both versions of the sources of lifeograph will be present in the OBS package and would also be packed together into the same SRC RPM. Is that correct ?
This is possible, however I think it makes more sense to keep this as two seperate packages. You can still have them in the same project and you can enable the build only for the working distro. In this way you keep clean spec files and your users find anyway the matching packages always in your project. Another option is of course to build against another project repo which provides the newer gtkmm for older distros. In this way your users would update it (if this is not causing trouble). I would think that building against GNOME:Factory/openSUSE_11.1 instead of against openSUSE:11.1/standard would do this, but I have not checked. You can edit this in your project meta data (osc meta prj home:PVince81 -e). bye adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Adrian, Thanks for your answer. I don't want to build against the GNOME factory project because I might choose to submit the package to an official repository So I think I'll simply make two packages out of it, as you suggested. Thanks, Vincent Petry Adrian Schröter a écrit :
Am Freitag, 18. September 2009 19:06:08 schrieb Vincent Petry:
Hi,
I have built a package for lifeograph version 0.4.1 in my home project (home:PVince81). The most recent version of this software, which is 0.5.4, only builds in openSUSE factory because it requires a higher version of gtkmm. For the other openSUSE versions like 11.1, only the version 0.4.1 can compile.
My question here is whether it is allowed, by convention, to mix such package versions ? It means I would have to modify the spec file to detect which openSUSE version we're building against, and switch the version field accordingly. It also means that both versions of the sources of lifeograph will be present in the OBS package and would also be packed together into the same SRC RPM. Is that correct ?
This is possible, however I think it makes more sense to keep this as two seperate packages.
You can still have them in the same project and you can enable the build only for the working distro.
In this way you keep clean spec files and your users find anyway the matching packages always in your project.
Another option is of course to build against another project repo which provides the newer gtkmm for older distros. In this way your users would update it (if this is not causing trouble).
I would think that building against GNOME:Factory/openSUSE_11.1 instead of against openSUSE:11.1/standard would do this, but I have not checked.
You can edit this in your project meta data (osc meta prj home:PVince81 -e).
bye adrian
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkq7X2MACgkQSSdxpfEEQEyEfQCgoxgwptxjOmFHFLfsVbPypXFd VrEAn1YAYGna09X7KLQBBf+aMBIHSEJX =LRpv -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter -
Vincent Petry