Juergen Daubert rote
On Mon, Jan 09, 2006 at 10:44:25PM +0100, Johannes Winkelmann wrote:
- udev enabled kernel/init scripts - ports tree using rsync by default - glibc 2.3.6 - xorg 6.9
sounds good, perhaps also including other "major releases" like - OpenSSL 0.9.8a
- gcc 4.0.2 ? - bash 3.1 ??
Probably not. Seems that we are doing this release without Per, so I'd suggest to have stability as the main goal. I prefer to have a release which allows the user the update from the cd without a fresh install. I don't now if this can be done in a sensefull way with gcc4.
are already compiled programs/working systems/libraries affected by upgrading to gcc4? if not, upgrading to gcc4 (and packages from the iso compiled by gcc4) should not be a problem (at least not from the users view) for the release numbering/naming scheme i'd expect that "minor" releases (like 2.2) lead to simple/straight forward updating procedures, whereas major releases (3.0) can imply some kind of "fresh install" when do those who dare to predict see that gcc4 becomes mandatory, even for the (up to now) most common scenario of x86 machines? [snip gcc4/bash details]
There's one important question we have to answer: do we want to move x11/firefox/gtk back to opt? As mentioned in the previous thread about this, I'd prefer to move them back, and so is Simone.
Fine with me, but they should be shipped on the cd. Meaning that we will have all core and some opt ports on the cd. If we go in that direction we should discuss what "some" means, I my opinion qt3 is one that should be added.
limiting by defined iso size? (is there a magic limit, like tiny CDs?) or functionality? compile time compromise? making a "poll" what should be included? i, for example, use crux only for routers and (internet)servers - but is introducing some kind of preselected packet lists of any use? for ex. core, router, server, desktop ... dejavu, somehow violates KISS
And if we are on cleaning-up core, we should consider about moving the following to opt too:
cdrtools, cpio, cvs, cvsup, gdb, linux-identd, pcmcia-cs, ppp, rp-pppoe, traceroute, wireless-tools, windowmaker, wvdial ... more ?
if "on the iso" is no longer the criteria for "core", we need some new, neat and nice criteria for core. (some "cruxish" critera) - bootimage/lifecd? - "getting online"? (would include ppp, rp-pppoe, wireless again) - common toolbase? - ... personally, i could live with some - "current core, without anything X-related or anything else bloating"
and of course all deps of x11/firefox/gtk but zlib and ncurses
e.g. fontconfig, freetype devfsd (not needed when switched to udev anyway) btw, is the list of programs ready to use when booting from the iso something what should be considered in this early stage? if so, i'd vote for something similiar to jaegers boot cd including sshd and dhcpclient sincerly, martin (irc: cohan)