| 1 |
On 01/22/2013 01:22 AM, Markos Chandras wrote: |
| 2 |
> On 22 January 2013 03:56, Zac Medico <zmedico@g.o> wrote: |
| 3 |
>> On 01/21/2013 07:45 PM, Mike Gilbert wrote: |
| 4 |
>>> My suspicion is that portage's environment save/restore process will |
| 5 |
>>> overwrite any setting I attempt to make on the destination host. |
| 6 |
>> |
| 7 |
>> If necessary, you can use /etc/portage/bashrc to override |
| 8 |
>> CONFIG_CHECK_FATAL for binary packages. Something like this would work: |
| 9 |
>> |
| 10 |
>> [[ ${EMERGE_FROM} == binary ]] && CONFIG_CHECK_FATAL=0 |
| 11 |
>> -- |
| 12 |
>> Thanks, |
| 13 |
>> Zac |
| 14 |
>> |
| 15 |
> |
| 16 |
> I guess the problem is when you create a binpkg and not when you |
| 17 |
> install it on the target. <wild idea> Would it be possible to make |
| 18 |
> this nonfatal if FEATURES contains "binpkg" or -B was passed to |
| 19 |
> emerge?</wild idea> |
| 20 |
|
| 21 |
The closest thing that PMS has defined is the MERGE_TYPE variable, which |
| 22 |
is supported since EAPI 4. This variable has 3 possible values: source, |
| 23 |
buildonly, or binary. Ebuilds can detect emerge --buildpkgonly by |
| 24 |
checking for [[ ${MERGE_TYPE} == buildonly ]]. However, for normal |
| 25 |
--buildpkg or FEATURES="buildpkg", the MERGE_TYPE is "source". |
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives