Gentoo Archives: gentoo-dev

From: "marco mascherpa (aka mush)" <mush@××××××.net>
To: gentoo-dev@g.o
Subject: [gentoo-dev] CVS versions and portage management
Date: Tue, 28 May 2002 10:34:07
Message-Id: 20020528173333.A18364@gladiator
1 hi,
2 it's the first time i write to this ML, altough i've been subscribed for a
3 while. i'm an italian guy, i'm studying information engineering in milan and i'm
4 a happy linux user. :) at the moment i'm enjoying a slackware, but some months
5 ago i found this gentoo and i think it's really awesome! it merges the goods of
6 both linux and BSD which i appreciate too! so i thought this is a great project
7 and i'm planning to join you developers as soon as my skills will permit it and
8 i will know enough of gentoo to avoid those RTFM questions. :)
9
10 now, let's go to the meat: last night i happened to install the CVS version of
11 gaim (the open source AIM clone) and suddenly i wondered how could gentoo
12 portage system manage the install/upgrade process of a CVS snapshot of an
13 application. it could seem a weird situation, why would we need to install the
14 CVS snapshot when we have the official releases? as you know better than me
15 sometimes some features we need are available only in the CVS version: for
16 example licq CVS version is perfectly compatible with the latest ICQ protocol,
17 but the official release isn't. but there are much more interesting cases than
18 this one, i guess :)
19
20 AFAIK the portege system cannot manage the CVS version of an app and decide, for
21 instance whether the version we are considering is older or newer than the
22 installed one: i can't upgrade a program with his CVS version.
23
24 i found two possible solutions to this problem:
25 - we could make a separate ebuild for every pregram: let's say we have the
26 ebuild of program foo, version 1.2.3: we have a foo-1.2.3-r1.ebuild for the
27 official release and a fooCVS-20020528-r1.ebuild for the CVS version. this would
28 lead to some coexistence inssues but it would be very easy to do and wouldn't
29 require any changes in the portage system.
30 - otherwise we could include in the ebuild a DATE variable wich will contain the
31 release date for official releases and the date of the CVS snapshot for CVS
32 versions. obviously this would mean some changes in the way upgrade and
33 dependencies are managed, but i think it wouldn't be too hard to implement.
34
35 i hope my thoughts will be useful in some way and again i congratulate you for
36 the optimum job you have made so far.
37 best regards
38 marco
39
40 --
41 Icy-Q 41982464
42 discussioni.org IRCoperator
43
44 "Have you seen my girl?
45 She's the one with the curly hair.
46 She was sitting just right over there,
47 now she's nowhere to be found."
48 Flying Blind

Replies