On Wed Oct 01, 2003 at 09:46:27PM +0200, Guillaume Rousse wrote: > > Suddenly I'm getting very tired of all of this again. Seems no matter how > > hard you try, someone has something negative to say without contributing > > something useful. > Vincent, i didn't intend to be rude, just to say that we first to have to make > the club work in a scalable and efficient manner first, and integrate it into > standard development process whereas it is currently completly run in a > parallel and amateurish way.
I agree with you on this, but you need to provide a way to make it better, or at least begin that process. Simply saying it's no good doesn't help. Yes, Club building has to be managed in a better way and, realistically, it should leverage the resources we have... you guys. For instance, if there was a simple way to do a build on klama for current contribs and handle the backport/build in a chroot on the same machine and "ftpclub" or "ftpclub-testing", "ftpclub-stable", "ftpclub-commercial", (you know what I mean) to get something into Club easily would be a bonus. Retrieval of packages is easy; voting is still a good idea. It's the submission/building/management process that is trying that should be fixed. > Automatic rebuilding of all cooker packages for current stable version should > be enough to solve contrib update problems IMHO. I don't think so. I do a lot of backports all the time... =) You cannot just grab something from "current" (by which I refer to cooker and contribs) and just rebuild it. That will not work. It is a manual process. I believe there needs to be some quality control, like there currently is with Club. Packages go in testing, people test, vote, etc. and if it's deemed stable enough, it goes into stable. Club packaging has to be different from "current" because your target is entirely different (people's production/stable systems, not developer systems). -- MandrakeSoft Security; http://www.mandrakesecure.net/ Online Security Resource Book; http://linsec.ca/ "lynx -source http://linsec.ca/vdanen.asc | gpg --import" {FE6F2AFD : 88D8 0D23 8D4B 3407 5BD7 66F9 2043 D0E5 FE6F 2AFD}
pgp00000.pgp
Description: PGP signature
