Re: Building same package twice and package forking
Luca <[email protected]> Sun, 12 Nov 2006 17:21:40 +0100
| Newsgroups | gmane.linux.distributions.rock.devel |
|---|---|
| Message-ID | <[email protected]> |
Luca wrote:
> Benjamin Schieder wrote:
>
>> On 12.11.2006 15:24:55, Luca wrote:
>>
>>
>>> Hi all!
>>>
>>> I'm trying with forking taking look to bash and linux, so I tried just
>>> to test these modifications for the lfs target:
>>>
>>> In gcc package directory I created a:
>>> -) preconfig.in
>>> if [ $SDECFG_TARGET = 'lfs' ] ; then
>>>
>>>
>> SDECFG? Are you sure you're using ROCK Linux?
>>
>>
>>
>>> if pkgcheck gcc X
>>>
>>>
>> At least in ROCK, gcc is not a package on its own, so this check will alsays
>> be false.
>>
>>
>>> then
>>> pkgfork gcc gcc-pass1 stages -X---5---9 priority 115.000
>>> pkgfork gcc gcc-pass2 stages -X---5---9 priority 115.000
>>> pkgenable gcc-pass1
>>> pkgenable gcc-pass2
>>> #pkgremove gcc
>>> fi
>>> fi
>>> (tried also with pkgcheck X instead of pkgenable and tried adding status
>>> X before stages)
>>> -) pkgmapper.in
>>> case "$pkg" in
>>> gcc[-pass{1,2}]
>>> pkg=gcc ;;
>>> esac
>>>
>>> and in the list of packages selected appear gcc, gcc-pass1 and gcc-pass2
>>> but it's marked with the "X" only gcc while the two forks are marked
>>> with "O".
>>>
>>>
>> btw, checking for a target in preconfig.in probably won't work.
>> Bette idea would be to always fork the gcc-pass[12] packages, disable them
>> per default, and then enable them in the targets *.in files.
>>
>>
>> Greetings,
>> Benjamin
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> rock-devel mailing list
>> [email protected]
>> http://www.rocklinux.net/mailman/listinfo/rock-devel
>>
>>
> Hi Benjamin,
>
> no, definitely my fault, I looked at too many things at the same time, I
> meant "ROCKCFG_TARGET='lfs'", at least because I saw no pkgfork
> function nor in OpenSDE neither in T2
> I'll try with your suggestions, I'll post a replay with the results.
>
> Thanks a lot,
> Luca
> _______________________________________________
> rock-devel mailing list
> [email protected]
> http://www.rocklinux.net/mailman/listinfo/rock-devel
>
>
Ok it seems to work, however I have another (hopefully last) question:
Now my package selection displays:
[packages]
X 012--5---- gcc
X 01---5-78- gcc=gcc-pass2
X 01---5-7-- gcc=gcc-pass1
[packages]
even if I passed different priority for each gcc.
Is it normal this behavior in displaying the package list or if I build
a fork gcc it builds it with the same priority of the original gcc?
Thanks in advance (and thanks Benjamin for precious help),
Luca