Mailinglist Archive: opensuse-marketing (277 mails)

< Previous Next >
[opensuse-marketing] Fwd: [opensuse-buildservice] how to make mediawiki packages
  • From: nmarques <nmo.marques@xxxxxxxxx>
  • Date: Wed, 13 Oct 2010 04:03:38 +0100
  • Message-id: <AANLkTi=kEzr4eZ63D2RGefBu==QRFcTo=S9c5SN-QYxC@xxxxxxxxxxxxxx>
2010/10/12 Johannes Weberhofer <jweberhofer@xxxxxxxxxxxxx>:

I'm currently trying to build new mediawiki packages which are FHS
compliant. I've nearly finished it, but I have one tiny problem:

Included in the sources there is one small tool which must be compiled and
is therefore architecture depended. Therefore the main package should go
into a noarch RPM, a small sub-package into an architecture specific RPM.

It seems, build support something like this since OSS 11.3, but only the
other way round: The sub-package can be noarch (which makes sense for docs I
think). Putting the following into the spec:

Name:           mediawiki
%if %{?suse_version} >= 1130
BuildArch:      noarch
%package texvc
%if %{?suse_version} >= 1130
BuildArch:      %{arch}

leads into
error: line 62: Only noarch subpackages are supported: BuildArch:      %{arch}

Try "%package -n texvc" ("%files -n", "description -n", for the
'sub'-package), be mindful that if you do such (-n) the package won't
inherit the prefix on the name.

Building a new package from the same spec should clear that out.


Do you see a way how to handle this problem nicely except splitting up the
package into two packages, one for the scripts, one for the binary?

Thank you and best regards,

Johannes Weberhofer
Weberhofer GmbH, Austria, Vienna
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx

To unsubscribe, e-mail: opensuse-marketing+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-marketing+help@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages