1 |
On Mon, Jun 05, 2006 at 02:24:24AM -0700, Brian Harring wrote: |
2 |
> On Mon, Jun 05, 2006 at 11:14:45AM +0200, Harald van Dijk wrote: |
3 |
> > On Mon, Jun 05, 2006 at 01:54:08AM -0700, Brian Harring wrote: |
4 |
> > > On Mon, Jun 05, 2006 at 10:19:41AM +0200, Harald van Dijk wrote: |
5 |
> > > > On Mon, Jun 05, 2006 at 03:45:50AM -0400, Mike Frysinger wrote: |
6 |
> > > > > On Monday 05 June 2006 02:07, Harald van Dijk wrote: |
7 |
> > > > > > Some gnustep stuff inherits cvs, but uses -D in the cvs options to |
8 |
> > > > > > always download exactly the same thing. |
9 |
> > > > > |
10 |
> > > > > then arent you just adding overhead to the poor gnustep cvs servers ? why not |
11 |
> > > > > roll a cvs snapshot tarball and distro via our mirrors |
12 |
> > > > |
13 |
> > > > Yeah, that'd probably be a better idea, but even if the current ebuilds |
14 |
> > > > are less than perfect, it seems like a valid use of the eclass to me, so |
15 |
> > > > making repoman error out is a bad idea, I think. A warning would be |
16 |
> > > > useful, though. |
17 |
> > > |
18 |
> > > 'Cept standards for ebuilds is typically http/https/ftp access for |
19 |
> > > fetching files- forcing pserver means people behind firewalls are |
20 |
> > > screwed... which is why non standard uri that is generally accessible |
21 |
> > > to users must be http/https/ftp, and if they aren't, upload the file |
22 |
> > > to the mirrors. |
23 |
> > > |
24 |
> > > Ebuilds might work, don't think they qualify as valid though- assume |
25 |
> > > initially it was easier to just copy the ebuild and lock the date; |
26 |
> > > doesn't make it valid though. :) |
27 |
> > |
28 |
> > I now checked: |
29 |
> > |
30 |
> > http://devmanual.gentoo.org/ebuild-writing/functions/src_unpack/cvs-sources/index.html |
31 |
> > |
32 |
> > If it's explained how to do it in the docs, I consider it valid, |
33 |
> > regardless of how bad an idea it may be. |
34 |
> |
35 |
> Except the doc specifically states they should be package.mask'd if |
36 |
> added; what that doc is talking about is vcs head ebuilds, not an |
37 |
> ebuild that's locked down to an exact rev/date. |
38 |
|
39 |
It first lists the disadvantages of CVS sources in general, and then |
40 |
the disadvantages of live CVS sources. If it only applied to live CVS |
41 |
sources, why would it split them up? |
42 |
|
43 |
> As mike said, why hammer on their servers? The ebuild isn't changing |
44 |
> (it's effectively a locked version), tarball it and upload it. |
45 |
|
46 |
And as I said, I agree that that would be a better idea. |
47 |
|
48 |
> Basically, the locked cvs version ebuild referenced above seems like a |
49 |
> lazy trick someone did to avoid rewriting it to drop the cvs usage. |
50 |
> |
51 |
> |
52 |
> > > Should be an error imo- there isn't any real requirement for a |
53 |
> > > cvs/git/darcs/subversion eclass consumer to be visible really. |
54 |
> > > ~harring |
55 |
> > |
56 |
> > Are you hoping for even ~arch cvs ebuilds to cause a repoman error? |
57 |
> |
58 |
> Original rules *were* that no vcs head based ebuild should be visible, |
59 |
> that it must be masked. Current devrel docs contradict that (those |
60 |
> docs bluntly are wrong- that change I don't think anyone ever agreed |
61 |
> to), devmanual states it correctly. |
62 |
|
63 |
The devmanual states that they should not "generally" be added to the |
64 |
tree softmasked or unmasked. It does not state that they should never |
65 |
be added as such at all. Or, in other words, there can be exceptions. |
66 |
|
67 |
> There's nothing wrong with vcs head ebuilds if they're masked; if |
68 |
> they're user visible (~arch), there is _no_ way to gurantee they're |
69 |
> actually sane (the source can and does change), that's why they're |
70 |
> suppossed to be masked. |
71 |
> |
72 |
> ~harring |
73 |
-- |
74 |
gentoo-dev@g.o mailing list |