1 |
On Tue, Oct 22, 2002 at 01:43:35PM -0600, Tom Syroid wrote: |
2 |
> I know you well enough that I can safely say you're not about to go off |
3 |
> using a new version of something on any kind of critcal box without testing |
4 |
> it first. So on the assumption that you have already discerned |
5 |
> program/tool/system utility is "ready for prime time", what's wrong with |
6 |
> simply edited the "frozen" entry in package.mask and installing it? |
7 |
|
8 |
There's nothing wrong with doing that, for myself, other than the |
9 |
annoying need to push out modified package.mask files to my systems |
10 |
after an 'emerge rsync'. (Well, and the security policy here at work |
11 |
doesn't allow for "unsupported" external packages, which our security |
12 |
team considers masked packages to be - but what they don't know won't |
13 |
hurt 'em.) |
14 |
|
15 |
But there are a couple of other problems. First and foremost, not every |
16 |
package held up by the freeze is in the portage tree and masked; I know |
17 |
of at least a few others that I use which are currently "out of date" |
18 |
because of the freeze. Sure, I could make ebuilds on my own - I have, in |
19 |
a couple of cases. |
20 |
|
21 |
Second, for me it's no big deal to edit the package.mask file or create |
22 |
custom ebuilds. Is that true of everybody? Is it even true of the |
23 |
majority, considering the general user population? I know from observing |
24 |
my local LUG that people start complaining when RedHat RPMs aren't |
25 |
immediately available for the latest cool software release - is the |
26 |
Gentoo community that much more forgiving? |
27 |
|
28 |
Finally, this doesn't answer my real question - why don't we know the |
29 |
answer to the question "how are the preparations for the release of 1.4 |
30 |
going?" Why are we not getting any communication from the development |
31 |
team? For that matter, why is there an ebuild freeze at all? If the |
32 |
portage tree weren't frozen, would we even care how long it took to |
33 |
release 1.4? |
34 |
|
35 |
> While I concur that the Gentoo development team as a whole could do a |
36 |
> better job of communicating TODO's and loose timelines to the community, I |
37 |
> don't see how a frozen Portage tree is preventing you from utilizing the |
38 |
> distribution in any way you heart desires. |
39 |
|
40 |
It's an inconvenience, not a barrier. My point was that we're not |
41 |
complaining about not getting "something free" on the schedule we |
42 |
demand. I don't need to use Gentoo at all; I could use FreeBSD, or |
43 |
stick with Debian or RedHat or any of a dozen other distributions, or go |
44 |
with a complete Linux-From-Scratch system. Gentoo is a convenience, a |
45 |
useful method of eliminating some of the work while still getting a |
46 |
system which does what I want. If the development team doesn't |
47 |
communicate TODOs and timelines and expectations, if they don't |
48 |
make use of their user community to help make the distribution better, |
49 |
the utility and convenience of using Gentoo is decreased as a result. |
50 |
|
51 |
Which is the real problem here - without the rapid updates and |
52 |
community-contributed ebuilds, Gentoo is not as useful as a |
53 |
distribution. |
54 |
|
55 |
-- |
56 |
Matt Beland |
57 |
matt@××××××××××××××.org |
58 |
http://www.rearviewmirror.org |