[clc-devel] Migration plan for CRUX 2.0
Hi everybody, many of you will surely know that Per has released a test version for CRUX 2.0 available at: http://www.fukt.bth.se/~per/crux/files/test/ ( for Per: works fine here with a fresh install, I was to scered by the release notes to try an upgrade ). Given that there's been some important change ( http://crux.fh-regensburg.de/cgi-bin/cvstrac/wiki?p=TwoZeroChanges ) and that many ports would need some adjustement, I was wondering if we have a simple plan for migration and testing before tagging the files for CRUX 2.0. I extended the "build all" script I used to test during the 1.2 >> 1.3 upgrade (now with real-time online progress and info). I plan a run as soon as the needed adjustements are done in all ports; the question is, should be begin tagging CONTRIB_2.0 just now or is it better to use a temporary tag for our tests? Other ideas? I think an upgrade path is important also for future releases, anyway, one spoon at a time, let's concentrate on 2.0 for now. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip@varlock.com
On Mon, 3 May 2004, Simone Rota wrote:
Hi everybody,
Hi,
many of you will surely know that Per has released a test version for CRUX 2.0 available at:
For those who didn't know, I uploaded the ISO last evening. I'll make an announcement about it on crux@fukt.bth.se when I get back home from work later today.
http://www.fukt.bth.se/~per/crux/files/test/ ( for Per: works fine here with a fresh install, I was to scered by the release notes to try an upgrade ).
Good to hear!
Given that there's been some important change ( http://crux.fh-regensburg.de/cgi-bin/cvstrac/wiki?p=TwoZeroChanges ) and that many ports would need some adjustement,
I'm not as confident that this test-ISO is as complete/finished as other test-ISOs have been in the past. I know for a fact that I will have to make a few updates and possibly make a test2-ISO before the final release. What I mostly feel unhappy about is the setup script/procedure, e.g. making a working upgrade procedure is hard. There are simply too many things that can go wrong or are tricky to fix. I've been thinking about making a complete re-design of the whole setup script/procedure, but never really got time for it. I would appreciate any ideas anyone might have regarding this, not just about the upgrade part and how to make that "safe", but also about the normal "install from scratch" procedure. In any case, starting to update CLC for 2.0 (using 2.0-test1 as the platform) should be fairly safe since I don't plan on making any major incompatible changes before 2.0-final. At the moment it feels like 2.0-final is about two weeks away. /Per
Hello, On Mon, May 03, 2004 at 03:55:14PM +0200, Per Liden wrote:
What I mostly feel unhappy about is the setup script/procedure, e.g. making a working upgrade procedure is hard. There are simply too many things that can go wrong or are tricky to fix. I've been thinking about making a complete re-design of the whole setup script/procedure, but never really got time for it. I would appreciate any ideas anyone might have regarding this, not just about the upgrade part and how to make that "safe", but also about the normal "install from scratch" procedure.
I don't think that's is really needed to have a bullet proof upgrade script. I self can live with the limitation that I have to install CRXU from scratch if I update from version x.a to x+1.a. The handbook says create separated partitions for system and data for later updates...
In any case, starting to update CLC for 2.0 (using 2.0-test1 as the platform) should be fairly safe since I don't plan on making any major incompatible changes before 2.0-final. At the moment it feels like 2.0-final is about two weeks away.
sounds great :-) Best regards, Tilo
On 05/03/04 15:55:14, Per Liden wrote:
I would appreciate any ideas anyone might have regarding this, not just about the upgrade part and how to make that "safe", but also about the normal "install from scratch" procedure.
about install from scratch i think that a precompiled kernel makes the install procedure more fast and easy in order i think that an "installed system" should be ever upgradable to "current" release throught the ports system and without any cdrom... so the online iso should be only a snapshot of the "current" crux version regards -- Giulivo Navigante GnuPG KeyID: E468396A
participants (4)
-
Giulivo Navigante -
Per Liden -
Simone Rota -
Tilo Riemer