Re: How to build noarch package on only certain architectures?

2011-05-18 Thread Dennis Gilmore
On Tuesday, May 17, 2011 10:43:47 AM Richard W.M. Jones wrote:
> On Tue, May 17, 2011 at 09:33:51AM -0400, Josh Boyer wrote:
> > On Tue, May 17, 2011 at 9:28 AM, Kevin Fenzi  wrote:
> > >> Is there some other way to add a noarch package that doesn't build on
> > >> some architectures?
> > > 
> > > Sadly this is a nasty situation. (I'm in the same boat with munin).
> > > 
> > > There are 2 answers, neither ideal (I'd love to hear better):
> > > 
> > > 1. Make your package archfull. Add ExcludeArch/ExclusiveArch.
> > > 
> > > 2. Leave it noarch and ExcludeArch: ppc64, then try and keep rebuilding
> > > it until you hit a non ppc builder.
> > 
> > 3. See if you can modify the package to do runtime determinism of
> > whether the dependency is there, and only use that functionality if
> > it's present.  Personally I think that if that can't be done, then
> > option 1 is the right way to go.
> 
> 4. Post a patch to fix RPM.
> 
> This is a bug or shortcoming in RPM.  It affected some mingw32
> packages as well IIRC -- they are noarch and can be built anywhere,
> but we wanted to %check them using wine which only runs on i386.
> 
> Rich.
make it archeful with a noarch subpackage that has the noarch bits. if you do 
it ExclusiveArch  for the base arch you want it built on  it would work as you 
want

Dennis


signature.asc
Description: This is a digitally signed message part.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: How to build noarch package on only certain architectures?

2011-05-17 Thread Richard W.M. Jones
On Tue, May 17, 2011 at 09:33:51AM -0400, Josh Boyer wrote:
> On Tue, May 17, 2011 at 9:28 AM, Kevin Fenzi  wrote:
> >> Is there some other way to add a noarch package that doesn't build on
> >> some architectures?
> >
> > Sadly this is a nasty situation. (I'm in the same boat with munin).
> >
> > There are 2 answers, neither ideal (I'd love to hear better):
> >
> > 1. Make your package archfull. Add ExcludeArch/ExclusiveArch.
> >
> > 2. Leave it noarch and ExcludeArch: ppc64, then try and keep rebuilding
> > it until you hit a non ppc builder.
> 
> 3. See if you can modify the package to do runtime determinism of
> whether the dependency is there, and only use that functionality if
> it's present.  Personally I think that if that can't be done, then
> option 1 is the right way to go.

4. Post a patch to fix RPM.

This is a bug or shortcoming in RPM.  It affected some mingw32
packages as well IIRC -- they are noarch and can be built anywhere,
but we wanted to %check them using wine which only runs on i386.

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine.  Supports Linux and Windows.
http://et.redhat.com/~rjones/virt-df/
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: How to build noarch package on only certain architectures?

2011-05-17 Thread Josh Boyer
On Tue, May 17, 2011 at 9:28 AM, Kevin Fenzi  wrote:
>> Is there some other way to add a noarch package that doesn't build on
>> some architectures?
>
> Sadly this is a nasty situation. (I'm in the same boat with munin).
>
> There are 2 answers, neither ideal (I'd love to hear better):
>
> 1. Make your package archfull. Add ExcludeArch/ExclusiveArch.
>
> 2. Leave it noarch and ExcludeArch: ppc64, then try and keep rebuilding
> it until you hit a non ppc builder.

3. See if you can modify the package to do runtime determinism of
whether the dependency is there, and only use that functionality if
it's present.  Personally I think that if that can't be done, then
option 1 is the right way to go.

josh
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel


Re: How to build noarch package on only certain architectures?

2011-05-17 Thread Kevin Fenzi
On Sun, 15 May 2011 16:40:50 -0700
Eric Smith  wrote:

> I'm trying to build Clapham for EPEL6.  Clapham is a noarch package,
> but it depends on Batik, which is ExclusiveArch: i686 x86_64.  When I 
> submitted a build with koji, it failed to build for ppc and ppc64 due
> to the missing dependency.
> 
> I tried adding the same ExclusiveArch to Clapham.  That causes errors 
> from rpm and koji.
> 
> Now I've tried adding ExcludeArch: ppc ppc64 s390 s390x.  Koji still 
> tries to build it for ppc64, and it still fails due to the missing 
> dependency.
> 
> Is there some other way to add a noarch package that doesn't build on 
> some architectures?

Sadly this is a nasty situation. (I'm in the same boat with munin). 

There are 2 answers, neither ideal (I'd love to hear better): 

1. Make your package archfull. Add ExcludeArch/ExclusiveArch. 

2. Leave it noarch and ExcludeArch: ppc64, then try and keep rebuilding
it until you hit a non ppc builder. 

I tried various other things, none of which worked. ;( 

kevin


signature.asc
Description: PGP signature
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel