| 1 |
On śro, 2017-05-24 at 11:54 -0400, Walter Dnes wrote: |
| 2 |
> On Wed, May 24, 2017 at 05:51:00AM -0400, Rich Freeman wrote |
| 3 |
> |
| 4 |
> > What value would be obtained by posting this stuff for user comment? |
| 5 |
> > I'd also note that only one of those was posted on -dev-announce for |
| 6 |
> > comment as far as I'm aware. Two are package/project-level changes |
| 7 |
> > which typically don't get wide discussion. |
| 8 |
> |
| 9 |
> I was using the Firefox PulseAudio event as another example of stuff |
| 10 |
> that happens in some obscure location that ordinary users don't know |
| 11 |
> about. It was https://bugzilla.mozilla.org/show_bug.cgi?id=1247056 |
| 12 |
> YES!!! It was done as a bug in the Firefox bugzilla. How many regular |
| 13 |
> users religiously follow that? |
| 14 |
> |
| 15 |
> There were some people who "upgraded" Firefox one day, and discovered |
| 16 |
> that sound no longer worked on it. It was done with so little |
| 17 |
> communication that several Firefox maintainers for various linux distros |
| 18 |
> (i.e. not exactly ordinary users) were unaware that they should set |
| 19 |
> PulseAudio as a hard dependancy for Firefox. |
| 20 |
> |
| 21 |
> An item I just remembered was the switchover from "/dev/hda" to |
| 22 |
> "/dev/sda". One day I upgraded (the kernel?), and got a panic at the |
| 23 |
> next bootup. Fortunately, I have a "Production" and an "Experimental" |
| 24 |
> kernel in my LILO menu, so I was able to reboot, and fall back to the |
| 25 |
> previous kernel. A new kernel always goes into "Experimental". I |
| 26 |
> "promote" the Experimental kernel to Production after it has run without |
| 27 |
> problems for a couple of weeks. |
| 28 |
> |
| 29 |
> Another one was when font packages stopped generating ISO8859-1 fonts |
| 30 |
> if you didn't add the "nls" USE flag. No news item. Xfreecell stopped |
| 31 |
> working because it couldn't find the font. |
| 32 |
> |
| 33 |
> The point I'm trying to make is that these kind of surprises should |
| 34 |
> not happen, be they OS-level or application-level. Regular users should |
| 35 |
> not have to follow this list. Even if you're not going to alter course |
| 36 |
> regardless of feedback, at least let users know so they're not caught |
| 37 |
> unawares. If nothing else, post news items to Gentoo-user ***AHEAD OF |
| 38 |
> TIME*** warning about changes like these. |
| 39 |
> |
| 40 |
|
| 41 |
...and all of this is completely irrelevant to the topic. This kind of |
| 42 |
information belongs in the news items, and for a few years now that's |
| 43 |
where you are expected to find them. |
| 44 |
|
| 45 |
-- |
| 46 |
Best regards, |
| 47 |
Michał Górny |
Archives