Re: [clc-devel] two collection of ports
![](https://secure.gravatar.com/avatar/4142d975fb1f6403dd0bb82ff4c4cfe8.jpg?s=120&d=mm&r=g)
dear Jurgen, i've understood the way to work of CLC with cvs; but i've not understood why a crux user have to re-install crux (the new version) to use the new ports even if he have upgraded his system. * juergen.daubert@t-online.de (juergen.daubert@t-online.de) ha scritto: | On Sat, Sep 06, 2003 at 11:47:28AM +0200, [slash] wrote: | | Hi Guiseppe, | | > I (and other italian crux users) think that isn't good to have two | > collection of contrib ports (1.1 and 1.2), because many crux users often | > upgrade the system by installing the new version of their packages then | > even if their system is marked "version 1.1" they have a system thet is upgraded | > like (or more than) a 1.2 ones. | | I'm sorry to say, but this shows me that you not really understand how | cvs and the tagging system we (CLC) use works. I'd suggest to read the | CLC cvs manual | | <http://clc.berlios.de/doc/clc-cvs.html> | | again and even look at Martin's fine cvs page at | | <http://rfhs8012.fh-regensburg.de/~opel/crux/clc/> | | btw, it's a _MUST_ for every CLC ports maintainer to update to every new | CRUX release asap. | | regards | Jürgen | | | -- | juergen.daubert@t-online.de | _______________________________________________ | clc-devel mailing list | clc-devel@lists.berlios.de | http://lists.berlios.de/mailman/listinfo/clc-devel
![](https://secure.gravatar.com/avatar/e550abd8e0394240c7e32acb8d07d1bc.jpg?s=120&d=mm&r=g)
On Sat, Sep 06, 2003 at 02:59:44PM +0200, [slash] wrote:
dear Jurgen, i've understood the way to work of CLC with cvs; but i've not understood why a crux user have to re-install crux (the new version) to use the new ports even if he have upgraded his system.
Because keeping the packages up-to-date isn't the full story. Major or even minor updates of the important system stuff like e.g. glibc/gcc/binutils will only happen at release boundaries. For such changes recompiling of the whole system is required. This is very time-consuming bootstrapping process, but gracefully done by Per for us. Greetings Jürgen -- juergen.daubert@t-online.de
participants (2)
-
[slash]
-
juergen.daubert@t-online.de