Mailinglist Archive: opensuse-packaging (109 mails)
< Previous | Next > |
Re: [opensuse-packaging] Duplicate -lang packages waste space
- From: Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx>
- Date: Mon, 15 Oct 2007 12:48:46 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0710151244590.22801@xxxxxxxxxxxxxxxxxxxxxxxxx>
On Oct 15 2007 09:41, Andreas Gruenbacher wrote:
>> 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
[...]
It is actually much easier: rpmbuild --target=noarch -bb bash.spec
In 10.2 this works most of the time, in 10.3 it works on less packages
(configure seems to dislike --target=noarch-suse-linux, and rightfully
so)
To answer Thorsten's question, just let %ifarch do its usual thing.
*All* that I want is to have specific packages *marked* noarch (i.e. rpm
--qf="%{ARCH}" returning noarch on them). So BuildArch: on subpackages
pretty much should work like the Group:, i.e. inherited from the main
package and possible to override.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
>> 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
[...]
It is actually much easier: rpmbuild --target=noarch -bb bash.spec
In 10.2 this works most of the time, in 10.3 it works on less packages
(configure seems to dislike --target=noarch-suse-linux, and rightfully
so)
To answer Thorsten's question, just let %ifarch do its usual thing.
*All* that I want is to have specific packages *marked* noarch (i.e. rpm
--qf="%{ARCH}" returning noarch on them). So BuildArch: on subpackages
pretty much should work like the Group:, i.e. inherited from the main
package and possible to override.
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
< Previous | Next > |