1 |
On Thursday 25 February 2010 04:03:16 Jeroen Roovers wrote: |
2 |
> Hello developers, |
3 |
> |
4 |
> this has annoyed me for a long time. |
5 |
> |
6 |
> restore_config() dies when it cannot find a saved config file, while |
7 |
> later on in any ebuild that uses savedconfig.eclass, it will save the |
8 |
> config file anyhow. That means it will not use an edited saved config |
9 |
> file during the first emerge, which is to be expected and should not be |
10 |
> fatal. |
11 |
> |
12 |
> The current forces you to emerge the same ebuild twice using _different_ |
13 |
> USE flags to achieve anything: |
14 |
> |
15 |
> 1. USE="-savedconfig" emerge cat/foo |
16 |
> 2. $EDITOR /etc/portage/savedconfig/cat/foo |
17 |
> 3. USE="savedconfig" emerge cat/foo |
18 |
> |
19 |
> This is quite illogical. |
20 |
|
21 |
|
22 |
Fixing this is fine my me. |
23 |
|
24 |
Daniel |
25 |
(illogical savedconfig.eclass author) |