1 |
I know I'm one of the new ones, and I shouldn't be complaining for this, but |
2 |
people please, pretty please, check what you remove out of p.mask.. if it was |
3 |
masked, there was probably a reason, check carefully before unmasking. |
4 |
Remember that when you get something out of p.mask, all users in ~arch are |
5 |
going to get it at the same time, it means that if something breaks, we have |
6 |
a broken ~arch tree at least, and while that's not the "stable tree", it's |
7 |
not good to have it broken this way. |
8 |
|
9 |
Rather, stick with something in p.mask for long times, and points people to |
10 |
unmask it to test it if bugs are fixed there, but _don't_ unmask it "and see |
11 |
what it happens". |
12 |
Better wait a week or two more, but get everything working, than having to |
13 |
deal with broken trees and people who complains. You might not care what |
14 |
users think and say, but many people (and I'm one of them) actually has to |
15 |
deal with users and gets annoyed by people asking "gee why this was done? it |
16 |
does not work!" and similar. And the upgrade/downgrade, especially for things |
17 |
that are linked in lots of programs, it's pretty annoying for devs, too. |
18 |
|
19 |
Just a friendly reminder, hoping that we won't see bigger problems. |
20 |
|
21 |
-- |
22 |
Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/ |
23 |
Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE |