Re: [gentoo-dev] Things one could be upset about

[Róbert Čerňanský]

On Sat, 24 Jan 2015 21:54:06 +0400
Alexey Mishustin <shumkar@×××××××.ru> wrote:

> 2015-01-20 14:42 GMT+04:00 Róbert Èeròanský <openhs@×××××××××.com>:
> > On Tue, 20 Jan 2015 11:08:19 +0300
> > Andrew Savchenko <bircoph@g.o> wrote:
> >
> >> On Tue, 20 Jan 2015 07:46:32 +0100 Róbert Èeròanský wrote:
> >> > On Tue, 20 Jan 2015 00:14:29 +0300
> >> > Andrew Savchenko <bircoph@g.o> wrote:
> >> > > On Mon, 19 Jan 2015 21:44:25 +0100 Róbert Èeròanský wrote:
> >> > For example, lets have following packages:
> >> >
> >> > - libbar
> >> > - libfoo with IUSE=bar, which depends on: bar? ( libbar )
> >> > - foo, which depends on: libfoo[bar]
> > [...]
> >> > New behaviour with automatic USE dependencies resolution:
> >> >
> >> > emerge -av foo
> >> > [ebuild  N     ] libbar
> >> > [ebuild  N     ] libfoo +bar
> >> > [ebuild  N     ] foo
> >> >
> >> > Now, you can hit Y if you agree what portage wants to do or N and
> >> > not to install foo at all.
> >>
> >> And if I don't agree? What if for some reason I don't want to
> >> have libfoo[bar] on my system. What If preferred solution will
> >> be not to use libbar at all and to use libclue instread?
> >
> > In this example, if you do not agree, you have no other option how
> > to install foo (with or without automatic USE deps).  Because foo
> > depends on libfoo[bar] unconditionally.
>
> Perfect! May be I will prefer to refuse to install that package, after
> seeing its dependencies.
>
> >> Yet again, Gentoo is all about choise. If someone wants that
> >
> > I agree, but I must say I am quite stunned that there are strong
> > voices against it.  I somehow thought that edit the overgrowing
> > package.use file upon each emerge world annoys anyone the same as
> > me.
>
> But for me this is one of the most useful and convenient options in
> Gentoo. Yes, I do edit package.use almost every emerge world. And I
> like to do it. And I don't want to delegate this right to any program
> - portage, or any other.

You would not loose that.  First of all, portage would do its changes
elsewhere (in /var).  Secondly, your settings in package.use would
still be respected.  But instead of portage telling you to edit
package.use it would show you required changes in emerge -av output.
If you do not like them then hit N and edit package.use, masks or
whatever.

In case of conflict, i.e. if portage would want to set a USE flag for a
package which you have disabled in package.use then it would fail
(similarly as it fails when some package has testing keyword or is
masked).  So if I have 'net-print/cups -usb' in package.use the
automatic USE depencencies would _never_ enable usb for cups.  But if I
have -python in _make.conf_ and want to emerge app-mobilephone/wammu
which depends on app-mobilephone/gammu[python] then portage would be
able to enable python for gammu.

The intention behind this automatic USE dependencies is to edit
package.use only when user wants, not when portage needs it.

Robert


-- 
Róbert Èeròanský
E-mail: openhs@×××××××××.com
Jabber: hs@××××××.sk