Re: [Cooker] The Weekly Cooker -- idea.
michael wrote: Ron: The requested URL /~ronst/rsync/troels_rsync3.pl was not found on this server. Apache/1.3.12 Server at www.ains.net.au Port 80 Huh? Everything is working correctly. Try: http://www.ains.net.au/~ronst/rsync/troels.rsync3.pl ie not a _ but a . But the preferred entry is via my web site and click appropriately. Firstly, read the reaedme.html.You will need to download the readme.html and the rsync_exclude files as well as troels.rsync3.pl. -- Ron. [au] Kindly note my new email address: [EMAIL PROTECTED] and new web site: http://www.ains.net.au/~ronst/
Re: [Cooker] The Weekly Cooker -- idea.
p == pablito [EMAIL PROTECTED] writes: p ... That way, you could have a daily cooker, and those who p have troubles making these iso files could download weekly iso p files. If the iso's were uniquely named (by date?) and it was accessble via HTTP, www.swarmcast.com could ease the pressure on the source cite -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 T(C)Inc Business Innovations through Open Source http://www.teledyn.com KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki
Re: Re: [Cooker] The Weekly Cooker -- idea.
The idea wasn't about saving bandwidth, but about increasing the testing time available for cooker. I mean 24 hours is just not enough time to give a distro any kind of full rigours of testing. A weekly ISO image, sanctioned by Mandrakesoft of the cooker distro would give a full week to testers to hack, as well as give those who like the hemoraging edge (downloading via. network every day) what they like as well. On Tue, 05 Jun 2001, Blue Lizard ([EMAIL PROTECTED]) wrote: Eaon wrote: That seems a wee bit daft. In exactly what way does it save bandwidth to have someone download 1 Gig of individual RPMs versus 1 Gig of ISOs? It's still 1 Gig. Anyway, I'm seeing ISOs there. They're kind of scattered - some in Mandrake-iso (SNF, freq, corpo) and some in Mandrake/iso (8.0) - but they are there. Eaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Blue Lizard Sent: Monday, June 04, 2001 5:15 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] The Weekly Cooker -- idea. The big guy at rpmfind got real mad and took off ALL isos cuz it took up so much bandwidth. See the note he left in the directory. Dont think he ever put em back up. This was one day after i was downloading them both at same time amounting to 600kbs. Dont ask me. And i saw some isos and figured the move-around would confuse the mirroring process enough to get em on there :)
Re: [Cooker] The Weekly Cooker -- idea.
Eaon wrote: That seems a wee bit daft. In exactly what way does it save bandwidth to have someone download 1 Gig of individual RPMs versus 1 Gig of ISOs? It's still 1 Gig. Users of my troels.rsync3.pl to download Mandrake trees and isos know that while you cannot change the size of an iso file, troels.rsymc3.pl permits you to do very selective downloads. For example, it comes from my web site (see below) arranged not to download any languages other than English, saving many hundreds of megabytes. Another tip: If you are not a developer, you can add: - *-devel-* to the rsync exclude list and so avoid downloading all the devel RPMs, again saving considerable download time and space. -- Ron. [au] Kindly note my new email address: [EMAIL PROTECTED] and new web site: http://www.ains.net.au/~ronst/
RE: [Cooker] The Weekly Cooker -- idea.
That seems a wee bit daft. In exactly what way does it save bandwidth to have someone download 1 Gig of individual RPMs versus 1 Gig of ISOs? It's still 1 Gig. Anyway, I'm seeing ISOs there. They're kind of scattered - some in Mandrake-iso (SNF, freq, corpo) and some in Mandrake/iso (8.0) - but they are there. Eaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Blue Lizard Sent: Monday, June 04, 2001 5:15 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] The Weekly Cooker -- idea. The big guy at rpmfind got real mad and took off ALL isos cuz it took up so much bandwidth. See the note he left in the directory. Dont think he ever put em back up. This was one day after i was downloading them both at same time amounting to 600kbs.
Re: [Cooker] The Weekly Cooker -- idea.
On Tuesday 05 June 2001 04:14 pm, Ron Stodden pointed out: Eaon wrote: That seems a wee bit daft. In exactly what way does it save bandwidth to have someone download 1 Gig of individual RPMs versus 1 Gig of ISOs? It's still 1 Gig. Users of my troels.rsync3.pl to download Mandrake trees and isos know that while you cannot change the size of an iso file, troels.rsymc3.pl permits you to do very selective downloads. For example, it comes from my web site (see below) arranged not to download any languages other than English, saving many hundreds of megabytes. Another tip: If you are not a developer, you can add: - *-devel-* to the rsync exclude list and so avoid downloading all the devel RPMs, again saving considerable download time and space. Ron: The requested URL /~ronst/rsync/troels_rsync3.pl was not found on this server. Apache/1.3.12 Server at www.ains.net.au Port 80 -- -m-
Re: [Cooker] The Weekly Cooker -- idea.
Eaon wrote: That seems a wee bit daft. In exactly what way does it save bandwidth to have someone download 1 Gig of individual RPMs versus 1 Gig of ISOs? It's still 1 Gig. Anyway, I'm seeing ISOs there. They're kind of scattered - some in Mandrake-iso (SNF, freq, corpo) and some in Mandrake/iso (8.0) - but they are there. Eaon -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Blue Lizard Sent: Monday, June 04, 2001 5:15 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] The Weekly Cooker -- idea. The big guy at rpmfind got real mad and took off ALL isos cuz it took up so much bandwidth. See the note he left in the directory. Dont think he ever put em back up. This was one day after i was downloading them both at same time amounting to 600kbs. Dont ask me. And i saw some isos and figured the move-around would confuse the mirroring process enough to get em on there :)
Re: [Cooker] The Weekly Cooker -- idea.
on the Weekly Cooker idea -- wouldn't it be possible to write a script that automatically builds iso files of the current cooker every week, and stick it on the mirror sites? The script would run at a certain time every week. That way, you could have a daily cooker, and those who have troubles making these iso files could download weekly iso files. although maybe the mirrors wouldn't be happy running scripts. -- -Original Message- From: Kyle Jacobs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wednesday, May 30, 2001 7:48 PM Subject: [Cooker] The Weekly Cooker I think its time we all took a look at the cooker release policy. What we appear to be doing now is releasing daily cookers. Each day, a new Distro for public testing, tinkering and revision.
Re: [Cooker] The Weekly Cooker -- idea.
The big guy at rpmfind got real mad and took off ALL isos cuz it took up so much bandwidth. See the note he left in the directory. Dont think he ever put em back up. This was one day after i was downloading them both at same time amounting to 600kbs.
Re: Re: [Cooker] The Weekly Cooker -- idea.
If these weekly files were auto-generated on a weekly basis (on the mirrors themselves), AND Bugzilla had a weekly entry for the weekly cooker (dated, of course), then this would be a perfectly viable alternative. On Mon, 4 Jun 2001, pablito ([EMAIL PROTECTED]) wrote: on the Weekly Cooker idea -- wouldn't it be possible to write a script that automatically builds iso files of the current cooker every week, and stick it on the mirror sites? The script would run at a certain time every week. That way, you could have a daily cooker, and those who have troubles making these iso files could download weekly iso files. although maybe the mirrors wouldn't be happy running scripts. -- -Original Message- From: Kyle Jacobs [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wednesday, May 30, 2001 7:48 PM Subject: [Cooker] The Weekly Cooker I think its time we all took a look at the cooker release policy. What we appear to be doing now is releasing daily cookers. Each day, a new Distro for public testing, tinkering and revision.
Re: [Cooker] The Weekly Cooker -- idea.
The big guy at rpmfind got real mad and took off ALL isos cuz it took up so much bandwidth. See the note he left in the directory. Dont think he ever put em back up. This was one day after i was downloading them both at same time amounting to 600kbs. So now we know who the guilty one
Re: [Cooker] The Weekly Cooker
Ainsi parlait michael : How about orouborous - it even sounds French!!! You seems to have a rather strange view of french language :-) Ainsi parlait Gary : h something about France, birthplace of Rin Tin Tin. That's just Tin Tin, and I wonder if there are enough characters in all those books to keep us in names for a long time. I'm think you're confusing Tintin, the boy-scout (which is belgian anyway), and Rintintin, the dog. -- Guillaume Rousse [EMAIL PROTECTED] GPG keys http://www.univ-reunion.fr/~grousse/gpgkeys.html
Re: [Cooker] The Weekly Cooker
1)U guys are too damn smart for me. 2)I think you should name this one after elven lord (was the name gilgalad or something? he's my first choice. following that:not obvious ones like elrond or aragorn, must be elven, or numenorian, or best yet since mandrake is the highest of linux distributions, one of the vala or maia until release 10 to be ihluvatar and then change the scheme. ) if u cant get the rights, try pestering Brian Herbert for the right to name after Leto Atreides. 3)I like my whitefish smoked and spread on a bagel. (can you sense the jew screaming out from inside?) 4)Metamorphosis is good hoyt, but not the others you mentioned. Nothing like those. 5)wait a min, what am i thinking, 10kg aint much fish at all. for some reason i was thinking of this massive whale of a whitefish that is more like 10k kg. g/l finding that though, and killing it. Dont ever wanna see u drunk, either. 6)Hmm, not entirely ecstatic about hurricane scheme idea. No 7)htf does that sound french? Well, there's my $.14 for the hour, unless i think of something else. Does Mandrakesoft have any openings for a more official form/job of heckling? -Blue
RE: [Cooker] The Weekly Cooker
That's just Tin Tin, and I wonder if there are enough characters in all those books to keep us in names for a long time. Once we run out of those we could move on to, um, damn, never remember the short one's name, anyway, what's his face and Obelix. The short Viking-looking guy and his big, fat buddy who's always carrying that big pillar around. As you can see, French immersion schooling had an eternal effect on me, if not a very deep one. :-) More coffee now. So Tin Tin's Belgian, eh? Interesting. Eaon
RE: [Cooker] The Weekly Cooker
On Fri, 1 Jun 2001, Eaon wrote: That's just Tin Tin, and I wonder if there are enough characters in all those books to keep us in names for a long time. Once we run out of those we could move on to, um, damn, never remember the short one's name, anyway, what's his face and Obelix. The short Viking-looking guy and his big, fat buddy who's always carrying that big pillar around. As you can see, French immersion schooling had an eternal effect on me, if not a very deep one. :-) More coffee now. Asterix Obelix seb
RE: [Cooker] The Weekly Cooker
At 11:35 AM 6/1/01, Eaon wrote: That's just Tin Tin, and I wonder if there are enough characters in all those books to keep us in names for a long time. Once we run out of those we could move on to, um, damn, never remember the short one's name, anyway, what's his face and Obelix. The short Viking-looking guy and his big, fat buddy who's always carrying that big pillar around. As you can see, French immersion schooling had an eternal effect on me, if not a very deep one. :-) More coffee now. So Tin Tin's Belgian, eh? Interesting. Rin Tin Tin was a dog in an american western series - U.S. Cavalry against the Indicans. The dog was always carrying messages past a gazillion indians and bringing the rescuers back just in time. If I remember it was in the 50's (and maybe the early 60's). Whichever it was, I was still living with my parents, so it was about then. David
Re: [Cooker] The Weekly Cooker
If I remember it was in the 50's (and maybe the early 60's). Whichever it was, I was still living with my parents, so it was about then. David Ladies and gentleman, what David doesnt want you to know is that he has no idea, he still lives with his parents. :)
Re: [Cooker] The Weekly Cooker
On Thursday 31 May 2001 06:42, you wrote: This is starting to make real sense uh-oh! Hi I think this scenario is somewhat more complicated. Pixel wrote about a month ago that the staff is mainly concerned by bugs reported to bugzilla. Today they are about 1865, noticed and then confirmed and later asigned to a staff person as his responsability. Thus the cooker list hangs in the air to some extent, there are no time for other things I guess. The daily cooker is to my understanding automatically revamped to be able to install as is. The time scedule for a new Mdk is about six month - this means that with a new compiler to become the base that all 2.4.x work is probably aimed to be phased down to a Mdk 8.2 and the new Cooker might have to stand on 2.5 and gcc 3.0 - this is just guessing. regards guran
Re: Re: [Cooker] The Weekly Cooker
If the cooker releases were reduced to just 1 or 2 a week, then the Mandrakesoft staff would actually have time to test, before releasing a cooker to ensure the minimal functionality of installing, and booting. I just think that a majority of problems that weren't addressed in the 8.0 release came because of the philosohy of the gaurenteed daily releases. 24 hours isn't enough time for people to do a good job until the next release. On Wed, 30 May 2001, Tim ([EMAIL PROTECTED]) wrote: This idea has one flaw that I forsee as a fatal one. What if that one release is a complete dud? There have been times in the past when a cooker release was a complete no go for some people. They needed the daily updates to get back to testing. Perhaps personally you could just upgrade files from time to time and then do a complete install once a week for testing purposes? Personally I like my hourly cron job running the rsync script to update my local tree. Just my 2 cents. -Tim And a weekly cooker doesn't mean a featureless one. We can throw all the new, bleeding and hemorrhaging edge technology we want into the weeks cooker, and spend the week not only addressing the regular components, but also the new- technology ones. If a weekly cooker sounds too sparse, how about two weekly cookers? One at the beginning of the week, one at the end? Just thought this might be a good idea.
Re: Re: [Cooker] The Weekly Cooker
What makes a new cooker? Some days I update and it's 25 megs. Today, after a few days wait, it was 330 megs. Maybe a better approach would be to wait as a user a week between updates...I am sure that as the daily changes are made, the people working on the packages appreciate the feedback and would prefer not to have to wait a whole week. My $.02 (US) -- On Thursday 31 May 2001 17:57, you wrote: If the cooker releases were reduced to just 1 or 2 a week, then the Mandrakesoft staff would actually have time to test, before releasing a cooker to ensure the minimal functionality of installing, and booting. I just think that a majority of problems that weren't addressed in the 8.0 release came because of the philosohy of the gaurenteed daily releases. 24 hours isn't enough time for people to do a good job until the next release. On Wed, 30 May 2001, Tim ([EMAIL PROTECTED]) wrote: This idea has one flaw that I forsee as a fatal one. What if that one release is a complete dud? There have been times in the past when a cooker release was a complete no go for some people. They needed the daily updates to get back to testing. Perhaps personally you could just upgrade files from time to time and then do a complete install once a week for testing purposes? Personally I like my hourly cron job running the rsync script to update my local tree. Just my 2 cents. -Tim And a weekly cooker doesn't mean a featureless one. We can throw all the new, bleeding and hemorrhaging edge technology we want into the weeks cooker, and spend the week not only addressing the regular components, but also the new- technology ones. If a weekly cooker sounds too sparse, how about two weekly cookers? One at the beginning of the week, one at the end? Just thought this might be a good idea.
Re: [Cooker] The Weekly Cooker
So sprach Kyle Jacobs am Thu, May 31, 2001 at 05:57:53PM -0400: release came because of the philosohy of the gaurenteed daily releases. 24 hours isn't enough time for people to do a good job until the next release. Uhm, where does Mandrake say anything like 'daily releases'? And, what's a release anyway? All I can find in Cooker are updated packages (including DrakX). And those packages are updated, whenever a packager feels like it. So, instead of a daily cooker, you've rather got a hourly cooker or even more frequent. And if only a package like GNOME, KDE, gimp is updated, there's no need for a tester to reinstall the whole system. Just upgrade the package and test. I get the feeling, that I'm misunderstanding you, somehow. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die günstige Art an Linux Distributionen zu kommen Uptime: 1 day 9 hours 4 minutes
Re: [Cooker] The Weekly Cooker
Hmm. Canada boy is making me hungry for either fried penguin or raw fish...? His idea of having a general mirror of weekly isos or something, Im not sure what, is nice. Kinda follows the philosophy behind the kc-cooker(slightly behind sched. thanks to vox) that people wanna be in the know or in this case (on the edge) but dont feel like being flooded with emails (or being on the hemoraging edge or updating constantly). Doesnt quit hold though in the way kc does because as said, some days it 25M of new rpms and after a while it 330M. It is a collection of apps, not one like w**doze. Common (apparently) misconception: Cooker is a daily scheduled thing. This is not true (unless i have been abducted by the government and placed in a hologram where I am thoroughly misled). A developer could make and upload program-.99-[1-28]mdk.rpm in one day and then wake up at 2am and, realizing it not work, recompile for -29mdk. Then another developer could say hey wtf are you doing and make -30mdk with installkernel put back in (haha, just kidding). So? What goes in? Remember that attempt at mdkfreq? Nice try...not Remember libext2fs-5mdk (the old school one)? I unfortunately was doing a fresh install at the time...you can see where this is going. That package took I while to get fixed (actually just downgraded) and remirrored thoroughly. I know, I was netinstalling for a few days! Finally did 80 and mdkupdated and figured out the prob. Then checked my mail and several others had figured it out too. Anyway, what if the broken package had been upgraded friday at 2, fishfried at 5, and everyone got through formatting and reinstalling until they had no initrd and couldnt boot to their scsi hds or use rescue disks from the install for the same reason? eh...sniff See with urpmi u can at least do some small quck precauitons to make sure nothing is obviously wrong, THEN reboot. And it easier to pinpoint the problematic package if u ssome who has it as an hourly cronjob or something frequenter than weekly. gee, had something else to say but cant remember, oh well, someone else will think of it (i shouldnt have started watching tv half through this). hmm Enterprise is feuding with cardacians. Must say if any frying of fish is to be done, it should be done by canadian cottage-dwellers or once a month (M$ has tought us traktopel.se traktopel.3e traktopel.4e traktopel prerelease 1,2 then the usual betas and release candidates like in the traktopel release. BTW anyone come up with name for 8.1 other than cooker? I loved the essay on mating habits of traktopels :).) Comm. worker Obrien served under the cardacian guest once. -Blue..sniff sniff sniff
Re: Re: [Cooker] The Weekly Cooker
I thought the testing was OUR job! We find the bugs, they squash the bugs, no? V. On Thursday 31 May 2001 04:57 pm, you wrote: If the cooker releases were reduced to just 1 or 2 a week, then the Mandrakesoft staff would actually have time to test, before releasing a cooker to ensure the minimal functionality of installing, and booting.
Re: Re: [Cooker] The Weekly Cooker
My comment was to the idea that a weekly release could be tested to ensure minimal functionality before being release for one weeks worth of testing. The originial idea is that only one or two cookers a week could not only simplify the development process, but also streamline it. Instead of having to file bug reports (That end up in the cooker mailing list) every day with every release, a single weekly release would give testers five whole days to throughly document AND test their bugs for things (like reoccourance), and five days to submit that info. The results could then go into the next weeks cooker, which could feature the fixes and the results from the previous weeks bug reports. One complaint is that some cookers don't function AT ALL, and that the next days cooker could be required to resume testing. My proposal was that the Mandrakesoft staff test at minimum the installer and boot process before releasing the weekly cooker, all other problems (including installation and boot problems not addressed already) could be submitted through Bugzilla by the public. On Thu, 31 May 2001, Vincent Meyer ([EMAIL PROTECTED]) wrote: I thought the testing was OUR job! We find the bugs, they squash the bugs, no? V. On Thursday 31 May 2001 04:57 pm, you wrote: If the cooker releases were reduced to just 1 or 2 a week, then the Mandrakesoft staff would actually have time to test, before releasing a cooker to ensure the minimal functionality of installing, and booting.
Re: [Cooker] The Weekly Cooker
B == Blue Lizard [EMAIL PROTECTED] writes: B Must say if any frying of fish is to be done, it should be done B by canadian cottage-dwellers Well, since I probably most resemble that remark, I'll tell you that, in Canadian cottage-country old-copper almost-56k end-of-the-line Internet, it would take me about a week just to get the thing into my CD-RW, and take you all another week to get it back out :) That said, if anyone wants a fried fish, they could bike up to the Bruce, we'll hammer one big mother whitefish to a maplewood board, lean it in a campfire, pop a keg, and sing songs of Herring under the limestone cliffs until dawn ;) -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 T(C)Inc Business Innovations through Open Source http://www.teledyn.com KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki
Re: [Cooker] The Weekly Cooker
On Thursday 31 May 2001 08:15 pm, you methodically organized electrons to state: BTW anyone come up with name for 8.1 other than cooker? I loved the essay on mating habits of traktopels :).) A while back, I suggested naming the releases after famous magicians (when Mandrake had meaning as the name of a Magician and the logo was a magician's hat and wand and Lothar was . . . ). The rejection of that schema was based on an infringement of copyrighted names. So how about getting back to the distro's roots and naming the release after magic tricks? Motorcycle to Nowhere, Metamorphosis and Cut and Restored Rope are names as cryptic as Traktopel. Or, how about naming them after French pioneers in aviation , science and so on? It might encourage some Merkins to learn something about France, birthplace of Rin Tin Tin. Hoyt
Re: [Cooker] The Weekly Cooker
h == hduff2 Hoyt writes: h . . . The rejection of that schema was based on an h infringement of copyrighted names. Damn lawyers. Fortunately, there are many public-domain magicians which can go all the way back to Albertus Magnus if you include those who practiced alchemy. Another scheme (the one used by OpenCola) follows the Hurricane convention where the first letter of the name tells the order within the year; OpenCola uses alchoholic beverages, so Amarretto was followed by Bourbon. h Or, how about naming them after French pioneers in aviation What ever you choose, you must be careful not to run out. h something about France, birthplace of Rin Tin Tin. That's just Tin Tin, and I wonder if there are enough characters in all those books to keep us in names for a long time. -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 T(C)Inc Business Innovations through Open Source http://www.teledyn.com KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki
Re: [Cooker] The Weekly Cooker
How about orouborous - it even sounds French!!! Hoyt wrote: snip A while back, I suggested naming the releases after famous magicians (when Mandrake had meaning as the name of a Magician and the logo was a magician's hat and wand and Lothar was . . . ). The rejection of that schema was based on an infringement of copyrighted names. So how about getting back to the distro's roots and naming the release after magic tricks? Motorcycle to Nowhere, Metamorphosis and Cut and Restored Rope are names as cryptic as Traktopel. Or, how about naming them after French pioneers in aviation , science and so on? It might encourage some Merkins to learn something about France, birthplace of Rin Tin Tin. Hoyt -- It requires a very unusual mind to undertake the analysis of the obvious. ANW
Re: [Cooker] The Weekly Cooker
I like the weekly cooker idea, except that it is very often too convenient to have the latest and greatest as soon as it's ready. I sympathize with the idea, though, I just don't want to loose the smooth flow of the cooker --- so I propose a third tier to our penguin food chain process: The Friday FishFry ;) How about keeping the cooker as that boiling pot of stone soup that is always on, always fresh, always ready for adding another turnip. Then, every friday, the cooker is mirrored to the Fryer (maybe the Fryer is also put into an ISO image for the truly adventurous. Create the Frying Pan CD's? I'd better stop while I'm ahead ;) This allows us to deploy a QA process on the whole-system integration (and interaction) of all packages, without upsetting the ecology of those who discover some bug _within_ an app, and need the fix asap. -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 T(C)Inc Business Innovations through Open Source http://www.teledyn.com KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki
Re: [Cooker] The Weekly Cooker
This is starting to make real sense uh-oh! what sayeth the (penguin)powers that be??? Gary Lawrence Murphy wrote: I like the weekly cooker idea, except that it is very often too convenient to have the latest and greatest as soon as it's ready. I sympathize with the idea, though, I just don't want to loose the smooth flow of the cooker --- so I propose a third tier to our penguin food chain process: The Friday FishFry ;) How about keeping the cooker as that boiling pot of stone soup that is always on, always fresh, always ready for adding another turnip. Then, every friday, the cooker is mirrored to the Fryer (maybe the Fryer is also put into an ISO image for the truly adventurous. Create the Frying Pan CD's? I'd better stop while I'm ahead ;) This allows us to deploy a QA process on the whole-system integration (and interaction) of all packages, without upsetting the ecology of those who discover some bug _within_ an app, and need the fix asap. -- Gary Lawrence Murphy [EMAIL PROTECTED]: office voice/fax: 01 519 4222723 T(C)Inc Business Innovations through Open Source http://www.teledyn.com KernelWiki Community Linux Docs: http://kernelbook.sourceforge.net/wiki -- It requires a very unusual mind to undertake the analysis of the obvious. ANW
