1 |
On Mon, 2006-06-05 at 15:16 +0200, Harald van Dijk wrote: |
2 |
> On Mon, Jun 05, 2006 at 01:51:31PM +0100, Ciaran McCreesh wrote: |
3 |
> > On Mon, 5 Jun 2006 14:41:43 +0200 Harald van Dijk <truedfx@g.o> |
4 |
> > wrote: |
5 |
> > | I then said that *you* say there can be legitimate reasons for them. |
6 |
> > | So why do *I* have to come up with examples of it? |
7 |
> > |
8 |
> > Well that's just it. I didn't say there were legitimate reasons, I just |
9 |
> > didn't commit myself to saying that there weren't. |
10 |
> |
11 |
> Fair enough, but if you read "can" as "could" in my posts, they still |
12 |
> make sense. |
13 |
> |
14 |
> Two reasons for CVS ebuilds that aren't hardmasked, by the way: |
15 |
> |
16 |
> One: see emacs-cvs-22*; it's more reliable than the emacs-22* snapshot. |
17 |
> (Something like this is only for ~arch.) |
18 |
|
19 |
> Two: when a specific revision is wanted, but snapshots aren't possible |
20 |
> for legal reasons. (This could even be marked stable.) |
21 |
|
22 |
If it can't be checksummed it should never be marked stable. *VCS* |
23 |
ebuilds simply can't be checksumed and there are far to many ways |
24 |
to abuse such things. Think MiM |
25 |
|
26 |
-- |
27 |
Ned Ludd <solar@g.o> |
28 |
Gentoo Linux |
29 |
|
30 |
-- |
31 |
gentoo-dev@g.o mailing list |