[opensuse-buildservice] Specify .spec file to use to build
I guess because of http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Using_differen... when you have a package with two spec files (e.g. binutils.spec and cross-x86_64-binutils.spec) nothing will build for a repository like "openSUSE_12.2", staying in status excluded. There is any way to avoid the excluded state other than removing the extra .spec files? Something like <build> <spec repository="openSUSE_12.2" file="binutils.spec"/> </build> ? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thu, Aug 02, 2012 at 10:08:30PM +0100, Cristian Morales Vega wrote:
I guess because of http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Using_differen... when you have a package with two spec files (e.g. binutils.spec and cross-x86_64-binutils.spec) nothing will build for a repository like "openSUSE_12.2", staying in status excluded.
It should pick binutils.spec if the build service package is named "binutils". If a package contains more than one specifle, its name matters. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 3 August 2012 09:25, Michael Schroeder <mls@suse.de> wrote:
On Thu, Aug 02, 2012 at 10:08:30PM +0100, Cristian Morales Vega wrote:
I guess because of http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Using_differen... when you have a package with two spec files (e.g. binutils.spec and cross-x86_64-binutils.spec) nothing will build for a repository like "openSUSE_12.2", staying in status excluded.
It should pick binutils.spec if the build service package is named "binutils". If a package contains more than one specifle, its name matters.
OK, let's use my specific user case to make this clear. I want the libraries compiled in my home repo to have DT_NEEDED entries for all the libraries they actually directly need. I don't submit a patch to Factory because there are good reason that's not the default. To do so I add a patch like this (https://build.opensuse.org/package/view_file?file=binutils-build-no-undefine...). But since I build for openSUSE_12.1 and openSUSE_12.2 I need two binutils packages, openSUSE:12.1/binutils and openSUSE:12.2/binutils. I can't have two packages with the same name in my home repo (sure, I could create different sub-repos specifically for this, I don't want to), so the packages with the links are named binutils-12.1 and binutils-12.2. Now, my binutils-12.2 package is building without problems. I don't have any real practical problem. My workaround is just to delete the cross-XXXX-binutils.spec packages: <link project="openSUSE:12.2" package="binutils"> <patches> <delete name="cross-alpha-binutils.spec" /> <delete name="cross-arm-binutils.spec" /> <delete name="cross-avr-binutils.spec" /> <delete name="cross-hppa-binutils.spec" /> <delete name="cross-hppa64-binutils.spec" /> <delete name="cross-i386-binutils.spec" /> <delete name="cross-ia64-binutils.spec" /> <delete name="cross-mips-binutils.spec" /> <delete name="cross-ppc-binutils.spec" /> <delete name="cross-ppc64-binutils.spec" /> <delete name="cross-s390-binutils.spec" /> <delete name="cross-s390x-binutils.spec" /> <delete name="cross-sparc-binutils.spec" /> <delete name="cross-spu-binutils.spec" /> <delete name="cross-x86_64-binutils.spec" /> </patches> </link> But since I think this is ugly (personal opinion anybody is free to disagree with) I wonder if there is a way to manually specify the .spec file to use. There is? -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Fri, Aug 03, 2012 at 10:06:46AM +0100, Cristian Morales Vega wrote:
On 3 August 2012 09:25, Michael Schroeder <mls@suse.de> wrote:
On Thu, Aug 02, 2012 at 10:08:30PM +0100, Cristian Morales Vega wrote:
I guess because of http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#Using_differen... when you have a package with two spec files (e.g. binutils.spec and cross-x86_64-binutils.spec) nothing will build for a repository like "openSUSE_12.2", staying in status excluded.
It should pick binutils.spec if the build service package is named "binutils". If a package contains more than one specifle, its name matters.
OK, let's use my specific user case to make this clear. I want the libraries compiled in my home repo to have DT_NEEDED entries for all the libraries they actually directly need. I don't submit a patch to Factory because there are good reason that's not the default. To do so I add a patch like this (https://build.opensuse.org/package/view_file?file=binutils-build-no-undefine...). But since I build for openSUSE_12.1 and openSUSE_12.2 I need two binutils packages, openSUSE:12.1/binutils and openSUSE:12.2/binutils. I can't have two packages with the same name in my home repo (sure, I could create different sub-repos specifically for this, I don't want to), so the packages with the links are named binutils-12.1 and binutils-12.2.
It should work if you name the packages "binutils.12.1" and "binutils.12.2". Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 3 August 2012 12:36, Michael Schroeder <mls@suse.de> wrote:
It should work if you name the packages "binutils.12.1" and "binutils.12.2".
No '-', no '_' but '.'? It's OK with me! Thanks. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (2)
-
Cristian Morales Vega -
Michael Schroeder