| 1 |
On Tue, 03 Jun 2014 15:24:22 +0300 |
| 2 |
Samuli Suominen <ssuominen@g.o> wrote: |
| 3 |
|
| 4 |
> On 03/06/14 15:08, Tom Wijsman wrote: |
| 5 |
> > On Tue, 3 Jun 2014 07:35:42 -0400 |
| 6 |
> > Rich Freeman <rich0@g.o> wrote: |
| 7 |
> > |
| 8 |
> >> This probably could have used a news item, as the change impacts |
| 9 |
> >> both stable and ~arch users. |
| 10 |
> > Are we going to write a news item every time systemd acquires a new |
| 11 |
> > mandatory relationship with a reverse dependency? |
| 12 |
> |
| 13 |
> IMHO, not every singular dependency change (even blocker) needs one. |
| 14 |
|
| 15 |
Regardless of that, most acquirements have lead to a news item. |
| 16 |
|
| 17 |
> For those failing to read `eix upower` |
| 18 |
|
| 19 |
That command doesn't tell anything helpful for this blocker. |
| 20 |
|
| 21 |
> or `emerge -C upower` |
| 22 |
|
| 23 |
For that you need to already know that you have to unmerge upower; it is |
| 24 |
also not going to help anything in terms of dependency calculation, |
| 25 |
except for a small amount of users that might have selected it. |
| 26 |
|
| 27 |
> or masking systemd, |
| 28 |
|
| 29 |
Masking systemd has the same effect as having udev selected; so, taking |
| 30 |
this action has zero effect and results in the blocker to still be |
| 31 |
there. The output has perhaps changed a little, the idea is the same. |
| 32 |
|
| 33 |
> or number of other ways the blocker can be solved, |
| 34 |
|
| 35 |
There is the problem, new Gentoo users can't solve it; that's why it's |
| 36 |
all over the place, as you've mentioned below. And some of it contains |
| 37 |
misinformation, like the gentoo-user thread you have responded to. |
| 38 |
|
| 39 |
Why do the users need to keep solving these nasty blockers? |
| 40 |
|
| 41 |
You could solve it if you use --tree --unordered-display; go through |
| 42 |
the dependency chain to check the reverse dependencies, write down what |
| 43 |
is going on and finally come to the conclusion of it all. But how are |
| 44 |
new users supposed to know all that? |
| 45 |
|
| 46 |
Why is --tree --unordered-display still not a default? |
| 47 |
|
| 48 |
In other words, why is the list of packages still flat by default? |
| 49 |
|
| 50 |
> the answer is in Gentoo news letter, |
| 51 |
|
| 52 |
Hidden somewhere in the middle, assuming users read about the update. |
| 53 |
|
| 54 |
> forums, |
| 55 |
|
| 56 |
As long as the activity of these topics last. |
| 57 |
|
| 58 |
> first hits in Google, |
| 59 |
|
| 60 |
Nothing found when I search for things like gentoo systemd blocker. |
| 61 |
|
| 62 |
> /topic of #gentoo at Freenode, MLs, pretty much everywhere. |
| 63 |
|
| 64 |
Which amounts to only a certain share of the users. |
| 65 |
|
| 66 |
> But news item has been planned all along for when UPower 0.99.0 goes |
| 67 |
> stable, propably |
| 68 |
> GNOME 3.12 and some 0.99.0 consumers, when there are enough steps to |
| 69 |
> accumulate as news worthy. |
| 70 |
|
| 71 |
Your reply doesn't answer the posed questions; instead, it demonstrates |
| 72 |
that it costs a lot more human resources the way we do things now. |
| 73 |
|
| 74 |
Users have to figure it out the hard way, developers then have to |
| 75 |
bring out the news the hard way; just like most of the previous times. |
| 76 |
|
| 77 |
-- |
| 78 |
With kind regards, |
| 79 |
|
| 80 |
Tom Wijsman (TomWij) |
| 81 |
Gentoo Developer |
| 82 |
|
| 83 |
E-mail address : TomWij@g.o |
| 84 |
GPG Public Key : 6D34E57D |
| 85 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |
Archives