Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaranm@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] creating ebuilds
Date: Tue, 06 Jan 2004 17:40:48
Message-Id: 20040106173919.3ff80bb6@snowdrop.home
In Reply to: Re: [gentoo-dev] creating ebuilds by Robert Cole
1 On Tue, 6 Jan 2004 09:26:50 -0800 Robert Cole
2 <robert.cole@×××××××××××××.com> wrote:
3 | > I'm sorry for that. It however can be a sign that the tree is not
4 | > ready for those ebuilds, or that they are in very low demand.
5 |
6 | If someone has gone their entire life using a rock to hammer nails and
7 | has never heard of a hammer before and thus doesn't have the demand
8 | for it does that mean that if they are told about the hammer they
9 | won't use it or have a demand for always having it?
10 |
11 | Sometimes you create demand where one doesn't currently exist by
12 | simply telling people about the hammer.
13
14 *bzzzzt*, silly analogy detected. Putting something in portage is not
15 telling people about it.
16
17 | If there is a way to make cvs ownership based that would be the
18 | easiest administration wise. As in the ebuild(s) I submit I have
19 | access to and nothing else.
20
21 Uh, that's still enough to screw up portage completely. One suitably
22 broken ebuild can still cause lots and lots of errors all over the
23 place.
24
25 I still don't see what's wrong with having a seperate repositry (eg
26 "breakmygentoo") for things that don't make it into the "official" tree.
27 (Well, actually, I see the whole "submitting bugs about things that
28 are caused by breakmygentoo ebuilds" issue, but a few messy public
29 executions by, say, Spider should sort that out... A 'tainted' flag on
30 emerge info would be good for that...)
31
32 --
33 Ciaran McCreesh
34 Mail: ciaranm at gentoo.org
35 Web: http://dev.gentoo.org/~ciaranm

Replies

Subject Author
Re: [gentoo-dev] creating ebuilds Robert Cole <robert.cole@×××××××××××××.com>