STan, First of all, the dependency tracking is going to be a real pain for several reasons. 1 Our rpms don't have correct deps yet, and 2. it's a pain in the butt to code and I don't feel like doing that ;) The build farm itself is nothing but a simple shell script, and a lot of it is done on the server with PHP. There's a lot of issues that need worked out. For instance user uploads windom-2.0, then uploads packages that need windom 2.0 to build. Does the build farm server automatically install the dep of windom 2.0. If it installs this, how does it handle conflicts? The approval system was designed to be quick and painless. It'll be finished soon and it's designed primarily as a tiny safeguard. Otherwise a rogue user can really wreak havoc since the system is so open to contribution. IMHO the approval system is necessary, even if it's causing further delays. I understand the theme isn't important ;) What do you mean about the continuous results without crashing. Are you upset about the fact that the build farm server is down? It's because I'm moving and it's unfortunate but it's going to be gone for about 2 more weeks, thereafter it will be back and several more build farm servers will be operational again. Thanks, Mark On Mon, 2006-03-27 at 21:35 -0500, Standa Opichal wrote: > Hi Mark! > > In my opinion what we need to get the build farm working according > to all the dependencies and perhaps also something to just drop the > *.src.rpm file and pick the binaries/build reports a day later if > appropriate. > > In my eyes all the approval and stuff around is not really necessary > for it to get going. The essential thing for it is to be able to > give results continuously not crashing the whole system. You can > simply limit write access using HTTP Basic or something really simple > to people that would be trusted to only do valid operations. But > it needs to take off... > > No theme can bother me until the functionality is usable. Until then > few people would even look at it. Perhaps open-sourcing the whole > beast would be a good idea so someone can actually help? > > Just my 2 cents. > > STanda > > > > -----Original Message----- > > From: mint-bounce@lists.fishpool.fi > > [mailto:mint-bounce@lists.fishpool.fi] On Behalf Of Mark Duckworth > > Sent: Sunday, March 26, 2006 1:13 AM > > To: Mint List > > Subject: [MiNT] Sparemint Site Work > > > > Hey guys, > > > > Some more work on http://dev.sparemint.org. > > > > Things worked on: > > Package Approvals, user preferences, 2 week login remembering > > now works > > (but will forget if you login from another machine due to the setup), > > some more theme polish... Still think it's kind of ugly. Was shooting > > for Hula style and it turned out like crap - but it's not done yet... > > User info page started, build farm display work. > > > > Things that need finished before it can go live: > > User preferences > > User approvals > > Package approvals > > Package disapprovals > > Package deletes and self-upload maintenance. (i.e. you > > upload a package > > and realize it's completely broken to the point where it must > > be deleted > > immediately. Normally you would just upload a fixed package > > which would > > override the current broken package). > > Transaction logger (will log all changes by all users to community > > resources (packages, etc) > > MediaWiki wiki. > > > > WHEN I actually have time and energy for the site, the stuff that > > remains should take no more than 10 hours of work... The question is > > having time, I'm quite busy with my real job and am moving. > > This is why > > the main build host, washi, is offline. If you upload > > packages, they'll > > have to sit in the queue to get built for a while. Sorry > > about that :-/ > > > > Comments welcome. Does it look poor? Please get picky, I want to > > produce something professional level for us. > > > > Thanks, > > Mark > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > >
Attachment:
signature.asc
Description: This is a digitally signed message part