| 1 |
On Wed, 04 Jun 2014 08:44:45 +0800 |
| 2 |
Patrick Lauer <patrick@g.o> wrote: |
| 3 |
|
| 4 |
> On 06/04/2014 08:24 AM, Tom Wijsman wrote: |
| 5 |
> > On Wed, 04 Jun 2014 07:55:50 +0800 |
| 6 |
> > Patrick Lauer <patrick@g.o> wrote: |
| 7 |
> > |
| 8 |
> >> On 06/03/2014 07:25 PM, Samuli Suominen wrote: |
| 9 |
> >>> |
| 10 |
> >>> On 03/06/14 14:40, J. Roeleveld wrote: |
| 11 |
> >>>> Would have been nice to fix all the dependencies BEFORE marking |
| 12 |
> >>>> the systemd- depending "sys-power/upower-pm-utils" stable. -- |
| 13 |
> >>>> Joost |
| 14 |
> >>> |
| 15 |
> >>> No clue what you mean, sys-power/upower-pm-utils doesn't depend on |
| 16 |
> >>> sys-apps/systemd, |
| 17 |
> >>> and whole Portage tree is converted to proper dependencies and the |
| 18 |
> >>> conversion went in |
| 19 |
> >>> the correct steps. |
| 20 |
> >> |
| 21 |
> >> The only step missing is: |
| 22 |
> >> |
| 23 |
> >> Mask the new version on all non-systemd profiles so that portage |
| 24 |
> >> doesn't try to install it |
| 25 |
> >> |
| 26 |
> >> (I wonder why systemd and the related stuff isn't masked on |
| 27 |
> >> non-systemd profiles anyway ...) |
| 28 |
> > |
| 29 |
> > There is no such thing as a non-systemd profile; a sub directory is |
| 30 |
> > a specialization, that doesn't mean that it parents suddenly become |
| 31 |
> > the opposite of that. No, the parents are just generalizations that |
| 32 |
> > aren't as specific as the sub directory. |
| 33 |
> |
| 34 |
> Since systemd needs special profiles to be easy to use ... |
| 35 |
|
| 36 |
No, these systemd profiles are only introduced for GNOME and KDE ... |
| 37 |
|
| 38 |
> ... it'd be the boring and easy way to restrict it to those profiles |
| 39 |
> so that dependency changes don't cause this needless amount of work |
| 40 |
> for users, and this indecent amount of mail on this mailinglist |
| 41 |
|
| 42 |
..., which means that your restriction doesn't hold ... |
| 43 |
|
| 44 |
> > Doing what you've suggested everywhere but in gnome/systemd and |
| 45 |
> > kde/systemd is a recipe to upset everyone whom runs systemd on |
| 46 |
> > another desktop environment than GNOME or KDE; so, that's not a way |
| 47 |
> > forward. |
| 48 |
> |
| 49 |
> I have no idea what you are trying to say, but there's a desktop |
| 50 |
> profile |
| 51 |
|
| 52 |
...; because systemd users also use the desktop profiles ... |
| 53 |
|
| 54 |
> > Another option is to create no-systemd sub directories; but such |
| 55 |
> > profiles will be highly controversial, besides helping the |
| 56 |
> > exponential grow of the profiles directories as well as be a |
| 57 |
> > non-default profile. |
| 58 |
> |
| 59 |
> The "default" is already that, all I'm suggesting is masking systemd |
| 60 |
> there so that portage doesn't needlessly antagonize users |
| 61 |
|
| 62 |
..., which makes your suggestion not an option. |
| 63 |
|
| 64 |
-- |
| 65 |
With kind regards, |
| 66 |
|
| 67 |
Tom Wijsman (TomWij) |
| 68 |
Gentoo Developer |
| 69 |
|
| 70 |
E-mail address : TomWij@g.o |
| 71 |
GPG Public Key : 6D34E57D |
| 72 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives