1 |
On Mon, Jul 09, 2001 at 10:23:41AM +0300, Dan Armak wrote: |
2 |
> Hi, |
3 |
> |
4 |
> Thanks for the reply. My most important question is still unanswered however: |
5 |
> the one about versioning. |
6 |
> To summarize my previous post: CVS-derived packages can't be compared, |
7 |
> version-wise, with 'release' versions. A CVS package installed _now_ is |
8 |
> always the latest version, since it comes straight from CVS. But, a CVS |
9 |
> package installed any number of days ago may or may not be new enough. So, we |
10 |
> can't know whether or not dependencies are being satisfied. (Unless we put a |
11 |
> timestamp on all release versions added to Portage.) |
12 |
|
13 |
You're right; that's one of the main problems I see in integrating CVS into |
14 |
Portage. There's just no way to get a good date for version comparision, at |
15 |
least if we rely completely on the CVS server. One option is for the user to |
16 |
provide a specific "lead version", like 2.1. Then the snapshot versions can be |
17 |
labelled 2.1_cvs20010709 and we can do some form of version comparison. In |
18 |
thinking about this whole CVS thing, I think it may be best if we simply add |
19 |
the ability to automate the creation a .tar.bz2 snapshot of the CVS archive, |
20 |
properly labelled. Then, it can be uploaded to ibiblio and installed the |
21 |
normal way. However, as long as we use some kind of "lead version" technique, |
22 |
I should be able to add proper version comparisons for cvs stuff, and thus |
23 |
solve the biggest problem. 2.1_cvs20010709 could be compared against 2.1, |
24 |
2.1_pre, 2.1_rc3, 2.1.1, etc. Because it's from CVS, I can have Portage assume |
25 |
that any 2.1 CVS release is newer than a 2.1 normal release (or even a p |
26 |
release). |
27 |
|
28 |
> A better idea I just had: if Portage can be _really_ integrated with cvs |
29 |
> management, we can fetch the _release_ version from CVS also! So, some |
30 |
> packages would go into "cvs mode", and would fetch either the specified |
31 |
> release version, or the latest release version, or the current version - |
32 |
> depending on the user's global/specific preferences. And then we could query |
33 |
> the CVS server for dates of release versions! |
34 |
> |
35 |
> What do you think? |
36 |
|
37 |
Well, I'm not sure how to do that. If you can provide some examples of bash |
38 |
commands that'll do that, maybe we can integrate it into Portage. Also, we |
39 |
need to have a reason to use a release version from CVS if there's a release |
40 |
.tar.gz file as well. Is the theory that the CVS release version will have the |
41 |
latest updates/bug fixes applied? |
42 |
|
43 |
Best Regards, |
44 |
|
45 |
-- |
46 |
Daniel Robbins <drobbins@g.o> |
47 |
President/CEO http://www.gentoo.org |
48 |
Gentoo Technologies, Inc. |