| 1 |
On Wed, 21 Jan 2015 01:57:27 +0000 (UTC) |
| 2 |
Duncan <1i5t5.duncan@×××.net> wrote: |
| 3 |
|
| 4 |
> Róbert Èeròanský posted on Tue, 20 Jan 2015 06:51:01 +0100 as |
| 5 |
> excerpted: |
| 6 |
> |
| 7 |
> > On Mon, 19 Jan 2015 20:51:31 +0000 Ciaran McCreesh |
| 8 |
> > <ciaran.mccreesh@××××××××××.com> wrote: |
| 9 |
> > |
| 10 |
> >> On Mon, 19 Jan 2015 21:44:25 +0100 Róbert Èeròanský |
| 11 |
> >> <openhs@×××××××××.com> wrote: |
| 12 |
> >> > From my point of view it would do much help if portage resolves |
| 13 |
> >> > USE dependencies automatically instead of telling the user to |
| 14 |
> >> > change USE flags manually (I am talking about bug #258371). |
| 15 |
> >> |
| 16 |
> >> This is only possible in carefully selected circumstances, and to |
| 17 |
> >> get it to work more generally would require a lot of hinting from |
| 18 |
> >> package maintainers. |
| 19 |
> > |
| 20 |
> > But portage already knows that. It tells the user which USE flags |
| 21 |
> > needs to be changed in order to emerge a package. It should just |
| 22 |
> > go one step further - to make the proposed change happen by itself. |
| 23 |
> |
| 24 |
> Actually, current portage (2.2.15 is what I have installed here ATM) |
| 25 |
> does exactly that, making changes to the appropriate package.* files |
| 26 |
> as necessary, mediated only by the usual CONFIG_PROTECT variables. |
| 27 |
|
| 28 |
No, no, no that is not the right solution. Portage should _not_ touch |
| 29 |
my precious config files crafted for many years. It should store the |
| 30 |
USE related dependencies info in its _internal_ structures (somewhere |
| 31 |
in /var/db/pkg I presume). Sorry I was not clear previously. Moreover |
| 32 |
it should be able to "depclean" them - revert the USE changes once the |
| 33 |
dependency is no longer needed (for example with new emerge option |
| 34 |
--use-depclean). Just like with standard package dependencies. |
| 35 |
|
| 36 |
> Since /etc/portage is CONFIG_PROTECTed by default, these changes |
| 37 |
> normally first appear in that feature's .* files, to be merged by the |
| 38 |
[...] |
| 39 |
> tolerable. As others in-thread have stated, we don't believe that's |
| 40 |
> something portage should be messing with. |
| 41 |
|
| 42 |
Totally agree, it should mess only with /var/db/pkg or so, not /etc. |
| 43 |
|
| 44 |
[... sniped great explanation of current testing portage behaviour in |
| 45 |
this regard; thanks for that, even though it is not what I crave for] |
| 46 |
|
| 47 |
Robert |
| 48 |
|
| 49 |
|
| 50 |
-- |
| 51 |
Róbert Èeròanský |
| 52 |
E-mail: openhs@×××××××××.com |
| 53 |
Jabber: hs@××××××.sk |
Archives