| 1 |
On Wed, Aug 24, 2011 at 12:56:17PM +0100, Ciaran McCreesh wrote: |
| 2 |
> On Wed, 24 Aug 2011 04:44:15 -0700 |
| 3 |
> Brian Harring <ferringb@×××××.com> wrote: |
| 4 |
> > Config arguably would benefit from env saving, but portage hasn't |
| 5 |
> > done it afaik, ever, so we can't really go retroactive on that one. |
| 6 |
> |
| 7 |
> Hrm. Paludis loads the env for vdb for pkg_info (for installed things) |
| 8 |
> and for pkg_config, but doesn't write it back again afterwards. Is this |
| 9 |
> not what Portage does? |
| 10 |
|
| 11 |
Doesn't save for config at the very least; actual loading, didn't |
| 12 |
check. As for load, well, trojan the env to find out (5am my time, |
| 13 |
going back to bed, someone else can figure it out). |
| 14 |
|
| 15 |
My inclincation is loading for info/config, saving for config, but |
| 16 |
portage long term behaviour here on the saving for config is likely |
| 17 |
going to be problematic. |
| 18 |
~harring |
Archives