1 |
On Thu, Sep 13, 2012 at 4:32 AM, Ulrich Mueller wrote: |
2 |
>>>>>> On Thu, 13 Sep 2012, David Leverton wrote: |
3 |
>> It's nice to be able to do |
4 |
>> local SANDBOX_WRITE=${SANDBOX_WRITE} |
5 |
>> and then allow bash to restore the old value at the end of the |
6 |
>> function, regardless of how it exits. It's not the end of the world |
7 |
>> to lose this, but it would be a bit of a shame IMHO - having to do it |
8 |
>> manually seems a little error-prone. |
9 |
> |
10 |
> Maybe we should just document the SANDBOX_* variables? Looks like the |
11 |
> easiest solution to me. |
12 |
> |
13 |
> The problem with adding an option to addwrite is that eclasses would |
14 |
> have to stick with the existing solution, or add a pointless case |
15 |
> distinction. Otherwise it won't work for all EAPIs. |
16 |
|
17 |
well, if you want to focus on the $now, then you're mostly correct. |
18 |
however, as we've done in the past, it's generally pretty easy to |
19 |
implement functionality in say eutils.eclass so that other places |
20 |
don't have to worry about different EAPI code paths. then in the |
21 |
$future, there is only the code provided by EAPI. |
22 |
-mike |