-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Folkert wrote: > On Tue, 2007-04-03 at 10:49 +0000, Joe Hart wrote: >> This point has already been answered in the Sidux forums. They have no >> plans of tracking testing. Sidux = Sid. > > I guess I made my point, but wrongly.
I understood you. > > CUT should be NEWER versions of things in Testing, perhaps everything > the same as Sid, but completely working all the time and every time. > > So, CUT would be a "cutoff line" for Sid's brokeness from time to time, > which I guess would actually make it not CUT, but CUS (Sid not stable). > > HA, I made a pun: Debian CUS > > But, it would be a more like, Continuously Installable and Usable Sid. A > staging point for Testing. Not Testing, which would be a snapshot of > CUS, where everything gets cleaned up and finalized for stable. That is exactly what Sidux is (at the moment). The few scripts they add are for doing things like running x applications as root (sux) providing a graphical password prompt when needing root commands (one at at time) (su-me), fixing a few things that are normally troublesome for new users like fonts, tv cards, and having meta-packages that are different than Debian's. The killer app for Sidux actually didn't make it into the first release, but should be in the next one. That is du-fixes-h2.sh, which is a script that ensures x is not running, checks for newer kernels, performs dist-upgrades (after checking for packages that may cause problems and putting them on hold), and installing graphics drivers. It also has a lot more functions like removing unneeded locals. It really is a masterpiece and it updates itself while running. > > Sort of like most GREAT development environments I've been a part of: > > Sandbox -> > Development -> > Testing -> > Quality Assurance -> > Production > > Where currently in Debian: > > Sandbox == The developers workstation > Development == Currently Sid > Testing == would be CUS > Quality Assurance == currently Testing > Production == Currently Stable > > Of course experimental would still be a branch, with changes being > merged back into Dev, but Dev (Sid) wouldn't have to freeze. Of course, > you would still have "Sandbox" for the developers to work > > But of course, this all is a moot discussion, Debian won't change. Then > again, maybe it might. You can never tell. It might. I actually wish it would because it just doesn't seem right to me that Sid should be stalled because Testing is frozen. I mean, things like Open Office 2.2 being released but the Sid package is 2.0.4. 2.1 was released a few months ago, but never made it into Sid because the fear that it might reach Etch. The two should not have anything to do with each other. AFAIK, this was the reason that Ubuntu was started in the first place, and probably why so many forks of Debian exist. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGEo9WiXBCVWpc5J4RAlb3AJ4gCtgC84JXp1a26lWxbbkFLI5LDQCgxp9O iSGJxwOdrErTlK3EsUzFSGE= =ypZ9 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
