| 1 |
On Sun, Jun 8, 2008 at 8:29 PM, Ciaran McCreesh |
| 2 |
<ciaran.mccreesh@××××××××××.com> wrote: |
| 3 |
[...] |
| 4 |
> This isn't as simple as you think, since quite a few of these utilities |
| 5 |
> are called using 'xargs' and so have to be binaries. Whilst Paludis can |
| 6 |
> deal with external binaries triggering a die because exheres needs it |
| 7 |
> (exheres has everything as fatal except where preceeded by 'nonfatal'), |
| 8 |
> I'm not sure that Portage can just now. |
| 9 |
|
| 10 |
I didn't understand you. Even if the external binary can't call die, |
| 11 |
what's to prevent the caller from dying based on the return value of |
| 12 |
the called binary? |
| 13 |
|
| 14 |
> Also note that quite a few packages rely upon the current nonfatal |
| 15 |
> behaviour, so it'd need to be an EAPI bump... |
| 16 |
|
| 17 |
It should not be necessary to define a new EAPI to make sure packages |
| 18 |
are not broken. If there really are a lot of packages that rely on the |
| 19 |
current behaviour, we can easily implement this in a phased manner: |
| 20 |
make it a QA notice to start with and make it default behaviour after |
| 21 |
3-6 months or whatever time period is suitable. |
| 22 |
|
| 23 |
BTW, do you have any examples of packages relying on non-fatal |
| 24 |
behaviour for do* stuff? It'd be interesting to see why it might be |
| 25 |
necessary. |
| 26 |
|
| 27 |
Regards, |
| 28 |
-- |
| 29 |
Arun Raghavan |
| 30 |
(http://nemesis.accosted.net) |
| 31 |
v2sw5Chw4+5ln4pr6$OFck2ma4+9u8w3+1!m?l7+9GSCKi056 |
| 32 |
e6+9i4b8/9HTAen4+5g4/8APa2Xs8r1/2p5-8 hackerkey.com |
| 33 |
-- |
| 34 |
gentoo-dev@l.g.o mailing list |
Archives