On Mon, Dec 26, 2016 at 09:59:54AM +0100, Michael Schwendt wrote: > On Sun, 25 Dec 2016 21:33:52 -0500, David Muse wrote: > > > I guess noarch packages shouldn't have any arch-specific dependencies. > > Is that correct? > > Yes. Umm really? Can you explain exactly what's wrong with this? I think the answer should be _no_ (ie. it's fine for noarch packages to have arch-ful Requires). Of course the dependencies must be available otherwise the noarch package cannot be installed. A typical example would be a -doc subpackage (noarch, built once and can be copied across architectures) documenting a C library (arch-ful, and built on each architecture). Unless you're talking about something different ... Rich. > Noarch packages may be built on any machine of any arch, they may be > copied to any repository for any arch, and they are supposed to be usable > with any arch. Unless "ExcludeArch" is set. > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-builder quickly builds VMs from scratch http://libguestfs.org/virt-builder.1.html _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
