Greg, The proper resource to use for auto-building is the SF Compile farm. CVS -> CF -> shell CVS -> CF -> FRS
# E3. Guide to the SourceForge.net Compile Farm https://sourceforge.net/docman/display_doc.php?docid=762&group_id=1 Note: we are currently using 1.1G of SF shell space. We are allocated 500MB. I'm working on the problem. On Wed, 2003-02-12 at 00:24, Greg Morgan wrote: > I cannot say this will work yet. phpWebSite uses a tmp directory for > working session files. > > dr_kludge@sc8-pr-shell1:/home/groups/l/le/leaf$ ls > cgi-bin devel htdocs log mirror pub tmp > dr_kludge@sc8-pr-shell1:/home/groups/l/le/leaf$ > > The edit session would be stored here through phpWebSite services. So > each user would have a unique edit session. If it is know what > individual packages make up a LEAF system, couldn't they be gunziped; > untared; have the modified files replaced? I sense the limitations > however. All appears to be well until you have to mount a bin file to > put it back together again. I don't don't now if phpws will let you do > that. I am sure SF would have problems with the web server using the > mount command. > > I am not even sure a user would find a punch list of items to edit back > on his live system useful. But that could be emailed to him/her after > filing in the information on the web page. > > I guess some more thought is required. Does the do you know if the > sloppy code is still around? -- Mike Noyes <mhnoyes @ users.sourceforge.net> http://sourceforge.net/users/mhnoyes/ http://leaf-project.org/ http://sitedocs.sf.net/ http://ffl.sf.net/ ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
