Mailinglist Archive: opensuse-buildservice (269 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Spec-File Question
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Fri, 5 Sep 2008 17:23:22 +0200
- Message-id: <200809051723.22856.adrian@xxxxxxx>
On Donnerstag 04 September 2008 16:25:32 Johannes Weberhofer, Weberhofer GmbH
wrote:
It is partly explained here:
http://en.opensuse.org/Build_Service/Tips_and_Tricks#_link_and__aggregate
Just added a link to official docu to the side bar, but informations about the
_link handling is missing there :/
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
wrote:
Is this feature and others which can be defined in the _link file and in
the xml describing the repository documented somewhere in detail?
It is partly explained here:
http://en.opensuse.org/Build_Service/Tips_and_Tricks#_link_and__aggregate
Just added a link to official docu to the side bar, but informations about the
_link handling is missing there :/
bye
adrian
Johannes
Adrian Schröter schrieb:
On Donnerstag 04 September 2008 11:07:16 Adrian Schröter wrote:
On Donnerstag 04 September 2008 10:53:31 Johannes Weberhofer, Weberhofer
GmbH
wrote:
Hello everyone!
I have started working with osb a month ago and I really love it! Well
done!
I have a specific question, maybe someone can answer it:
I want two build two versions of an executable file and provide this
file via different rpms (At the end three packages shouldresult:
package, package-cgi-withfeature, package-cgi-withoutfeature).
Is there any way to handle such things within _one_ spec file? I can
configure/make the package twice and copy the resulting file somewhere,
but I don't know a way to bring it back to it's position in the
filesystem before I enter the related %file section.
hm, you can via two repositories. Having something like
Actually it works also with a source link:
%if %{?small_build:1}0
Name: small
%else
Name: big
%endif
Than create another virtual package in the same project with a source
link. The source _link file should look like:
<link project="myproject" package="theotherpackage">
<patches>
<topadd>%define %small_build 1</topadd>
</patches>
</link>
So the second build will get the macro defined. You need to create the
source link only once and can work only on the spec file in the other
package.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |