On Thu, Oct 22, 2015 at 12:38:33PM +0200, Johannes Meixner wrote:
I have a package "foo" in a development project where also a package "bar" in that same project exists that is used to build "foo".
I like to specify in my package "foo" not to use "bar" from that development project but to use "bar" from the repository that is used to build "foo".
Can I specify that in my package "foo" and if yes how can I do it?
I have "sane-backends" in its development project "graphics" where also "libgphoto2" exists.
sane-backends needs libgphoto2 to build.
I build sane-backends also for released openSUSE versions.
Now when a user of a released openSUSE version likes to install sane-backends from the graphics project he also needs libgphoto2 from the graphics project.
But unfortunately the newest version of libgphoto2 from the graphics project cannot be installed into released openSUSE versions without dependency issues because other packages in the released openSUSE versions need an older version of libgphoto2.
If I could build sane-backends in the graphics project not with libgphoto2 from the graphics project but with libgphoto2 from the repository that is used to build sane-backends, then sane-backends would require the libgphoto2 version of the released openSUSE versions and users could install sane-backends from the graphics project into their released openSUSE versions without dependency issues.
As a workaround the maintainer of libgphoto2 has now disabled in the graphics project that libgphoto2 is used for build for released openSUSE versions but this has the drawback that libgphoto2 is no longer used for build for all packages in the graphics project.
What I would prefer is that I could specify only in sane-backends how exactly I like to have this particular package built.
(just fyi) libgphoto2 is still used for in graphics for Tumbleweed, Factory and Leap which should be compatible in regards to the libgphoto2_port.so requirement.