1 |
Doug Klima <cardoe@g.o> posted 47C8E29A.2020003@g.o, |
2 |
excerpted below, on Fri, 29 Feb 2008 23:59:06 -0500: |
3 |
|
4 |
>> Is direct upgrade from previous baselayout-2.0.0-rcX going to be |
5 |
>> supported? I was running that for some time and just now added and |
6 |
>> upgraded to the via layman version. There's a blocker, of course, as |
7 |
>> openrc is now providing most of the files that baselayout did. |
8 |
> |
9 |
> You just answered your own question. If another package now provides |
10 |
> files that an existing package provides, they must be blockers. |
11 |
|
12 |
Thus the "of course"... |
13 |
|
14 |
> Considering baselayout-2.0.0_rcX was a masked version and never |
15 |
> recommended, it's also not in the direct upgrade path. The proper |
16 |
> upgrade is what you've detailed out below. Such are the risks when you |
17 |
> unmask a package and install it on your machine. |
18 |
|
19 |
Which is why I'm not particularly complaining, just asking. |
20 |
|
21 |
Practically speaking, while it's not required by any means, some devs |
22 |
choose to acknowledge the symbiotic relationship between pre-release |
23 |
testers willing to take that risk and do the work to find and file bugs, |
24 |
thus helping to make the general release far less buggy, and the devs who |
25 |
depend on such testers for that function. The testers do a favor for the |
26 |
devs with all that early testing and bug filing (sometimes with patches), |
27 |
and many devs choose to return it by providing a working upgrade path |
28 |
from the pre-releases to the general release. Among other things, it |
29 |
makes for happier testers, who are then likely to be repeat testers, the |
30 |
next time an upgrade comes along. |
31 |
|
32 |
It's also worth mentioning that a call for testers went out, so it's not |
33 |
as if those that answered it, particularly if the DID actively look for |
34 |
and file bugs as they found them, were doing it entirely of their own |
35 |
accord. Again, it's doing the developer a favor, so it's a nice gesture |
36 |
if the developer chooses to return the favor by smoothing the upgrade |
37 |
path. Not something he has to do, but something he /can/ do, to increase |
38 |
the chances of folks who already know the process again taking him up on |
39 |
the invitation, the next time he needs something tested. =8^) |
40 |
|
41 |
So anyway, I thought it was worth asking about, in case it had slipped |
42 |
his mind or he hadn't thought of it. No big deal either way, but it'd be |
43 |
a nice gesture if it's not too difficult to setup. |
44 |
|
45 |
-- |
46 |
Duncan - List replies preferred. No HTML msgs. |
47 |
"Every nonfree program has a lord, a master -- |
48 |
and if you use the program, he is your master." Richard Stallman |
49 |
|
50 |
-- |
51 |
gentoo-dev@l.g.o mailing list |