And because there are so many different CPU (aka instruction set) architectures, VERY few packages can get the hallowed noarch moniker. To the best of my knowledge, a package can ONLY contain the "noarch" tag if the package contains absolutely NO runtime binaries. A noarch package can contain "binary" files, like a gzipped man page, for example, but it could never contain any pre-compiled application or utility. That's why noarch packages are things like source code, documentation, support files, multimedia files, etc. BB. > > Because a binary x86 executable is not valid for say a SPARC platform, > > or ALPHA, or even ia64. 'noarch' means that it'll work across every > > arch, sparc/alpha/x86/etc... .i386 means that it'll work across all x86 > > compatible archs.. see the point? > > Ok, that explains it more. I forgot about those other archs and guess that > answers the question. I knew I'd think of it. -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
