[opensuse-buildservice] Build time dependency resolution (multiple version support)
Hi, I'm currently running into the issue described here: http://lists.opensuse.org/opensuse-buildservice/2014-01/msg00156.html The following statements seem to be to be true: 1) In a given distribution, only the most recently built version of a package will be available to satisfy BuildRequires 2) If a mis-matched version of a BuildRequires dependency exists in a distribution in a package's project, no other project's distributions will be searched for that dependency, even if the BuildRequires specifies a version available in a different distribution that is in the repository search configuration Can someone please confirm they are correct? If they are correct, are there any plans to support multiple versions of builds for satisfying BuildRequires? I started to look at the code around this and it seems pretty dense - what direction would you point someone in if they wanted to modify this behavior? The only other options I can think of are all very cumbersome in terms of administrative overhead within OBS. Thanks for your help. Andy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Andrew Davidoff <davidoff@qedmf.net> Mon, 31 Mar 2014 21:33:37 +0300:
Hi,
I'm currently running into the issue described here:
http://lists.opensuse.org/opensuse-buildservice/2014-01/msg00156.html
The following statements seem to be to be true:
1) In a given distribution, only the most recently built version of a package will be available to satisfy BuildRequires
2) If a mis-matched version of a BuildRequires dependency exists in a distribution in a package's project, no other project's distributions will be searched for that dependency, even if the BuildRequires specifies a version available in a different distribution that is in the repository search configuration
Can someone please confirm they are correct?
If they are correct, are there any plans to support multiple versions of builds for satisfying BuildRequires? I started to look at the code around this and it seems pretty dense - what direction would you point someone in if they wanted to modify this behavior? The only other options I can think of are all very cumbersome in terms of administrative overhead within OBS.
Thanks for your help. Andy
Hello! You completely right. Usually such packages have different names: see allegro packages at games f.e.: https://build.opensuse.org/package/binaries/games/allegro?repository=openSUS... https://build.opensuse.org/package/binaries/games/allegro5?repository=openSU... https://build.opensuse.org/package/binaries/games/allegro52?repository=openS... -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Mar 31, 2014 at 2:40 PM, Dmitriy Perlow <dap@open.by> wrote:
Hello!
You completely right. Usually such packages have different names: see allegro packages at games f.e.: https://build.opensuse.org/package/binaries/games/allegro?repository=openSUS... https://build.opensuse.org/package/binaries/games/allegro5?repository=openSU... https://build.opensuse.org/package/binaries/games/allegro52?repository=openS...
Thanks Dmitriy. This may be too much administrative overhead for me, but I'll have to think more about it. Are there plans to support multiple versions for build time dependencies? If not, short of reading through bs_sched and related code, is there a specific area in the codebase I'd look at if I wanted to modify this behavior? Thanks again. Andy -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 2. April 2014, 15:18:54 wrote Andrew Davidoff:
On Mon, Mar 31, 2014 at 2:40 PM, Dmitriy Perlow <dap@open.by> wrote:
Hello!
You completely right. Usually such packages have different names: see allegro packages at games f.e.: https://build.opensuse.org/package/binaries/games/allegro?repository=openSUS... https://build.opensuse.org/package/binaries/games/allegro5?repository=openSU... https://build.opensuse.org/package/binaries/games/allegro52?repository=openS...
Thanks Dmitriy. This may be too much administrative overhead for me, but I'll have to think more about it.
Are there plans to support multiple versions for build time dependencies?
This conflicts a bit with the requirement to be able to downgrade rpms again in upper layers in case of problems. And since this problem exists only when the packages are not prepared for parallel installation it is a problem which would also exist on the end-user system. He would run also into problems installing both packages or even worse one package would corrupt the other one. With the result of hard to debug errors...
If not, short of reading through bs_sched and related code, is there a specific area in the codebase I'd look at if I wanted to modify this behavior?
Thanks again. Andy
-- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Andrew Davidoff -
Dmitriy Perlow