On Fri, Feb 13, 2009 at 11:12:00AM +0100, Florian Festi wrote: > As another solution for this problem we (ehm, Panu) will backport a check > that will make noarch packages (both regular and noarch) fail to build if > they contain binaries (==colored files==the right thing to do even for > emulators, bioses, cross compilers, ...[1]). This additional check will > be in place before koji will be updated [2]. How will this work with proprietary software authors who want to distribute their software as RPMs? (Or, more realistically, for people who package up proprietary software as RPMs for ease of installation)? What counts as 'binary'? What about generated code for example (may I introduce configure scripts). If a binary is included in the source tarball, but only used for building or not used at all, and doesn't get propagated to the output RPMs, does that count? Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
