1 |
Robert Thomas <rwt@×××××××××.edu> writes: |
2 |
|
3 |
> Instead of having a separate package for a cvs version of a package, |
4 |
> why not consider the cvs version to be the latest version of a |
5 |
> package, but always marked unstable? Since the cvs version of a |
6 |
> package usually overwrites the existing version, the old version |
7 |
> should be automagically unmerged. For example, in the case of gaim and |
8 |
> gaim-cvs, if the cvs version of gaim is installed, the stable version |
9 |
> should be unmerged as if it was an old version of the package. Perhaps |
10 |
> there is another way to manage this. |
11 |
> In the case of binary packages (like openoffice-bin), they should also |
12 |
> be considered to be the same package, but still kept separate in some |
13 |
> way. |
14 |
> Perhaps another USE flag? |
15 |
> # USE="bin" emerge openoffice |
16 |
> |
17 |
> Or maybe cvs could be a new keyword: |
18 |
> # ACCEPT_KEYWORDS="cvs" emerge gaim |
19 |
> |
20 |
> Ok, I really am talking out of the wrong orifice here, and I know that |
21 |
> these ideas are probably a misuse of USE flags and KEYWORDS. I would |
22 |
> just like to know if something like this could work (not necessarily |
23 |
> the way I've described it, perhaps a different extention to the |
24 |
> version calculating routine altogether), or if there is a reason these |
25 |
> packages are managed the way they are (by "these" I mean all packages |
26 |
> ending in "-bin" or "-cvs"). |
27 |
|
28 |
|
29 |
>From a developer's standpoint, having one ebuild for both release and |
30 |
CVS versions would usually clutter the ebuild substantially. At least |
31 |
I *know* this would be the case with the emacs and emacs-cvs ebuilds. |
32 |
|
33 |
Secondly, there's no reason why a CVS ebuild should override the |
34 |
release version you might already have installed. There just happens |
35 |
to be no policy (afaik) on this particular matter. Technically, I |
36 |
think its the way to go (ie. simultaneous version). |
37 |
|
38 |
Matt |
39 |
|
40 |
-- |
41 |
Matthew Kennedy |
42 |
Gentoo Linux Developer |
43 |
|
44 |
|
45 |
-- |
46 |
gentoo-dev@g.o mailing list |