On Monday 15 October 2007 08:38, Thorsten Kukuk wrote:
I think this idea was already rejected upstream, since RPM has no chance to make sure that the content is really noarch.
Ah, okay. It's quite possible that someone brought up this argument, but the argument doesn't hold water. Creating noarch packages that contain architecture specific files is easy, and there is little that can be done about it.
If you build a normal noarch package, all arch specific commands like "ifarch" are disabled and will be ignored. How to do that for a subpackage?
It's a pointless exercise. The noarch files need to be built somehow, and if
you turn of everything that might result in an architecture dependency, then
this also includes all nontrivial tools for producing architecture
independent files. You really need to know what you are doing when creating
noarch packages.
Name: not-noarch
Summary: Not a noarch package
Version: 1
Release: 0
License: GPL
Group: Application/Text
BuildArch: noarch
BuildRoot: %{_builddir}/%{name}-root
%description
Creating false %%noarch packages is easy...
%build
cat > hello.c <