At 2002-02-27 11:04 -0600, Charles Steinkuehler wrote: > > Suggestions and comments on the proposed change are welcome. ><snip> > > >I hope all has been going well for your projects lately -- has been > > >a while since we've talked. As part of our periodic disk usage > > >quota checks, we noticed that leaf is once again using a fairly > > >large chunk of disk for disc images, etc. Would it be possible to > > >offload these to the file release system, and take other steps to > > >reduce the amount of disk used by the leaf project as to bring it > > >back in check? > >Any chance we can get support for subdirectories on the download >server? I think our problem is we've got *TONS* of package files, as well >as many different kernel trees, disk images, &c. It's hard enough to >organize in a meaningful way on the shell server...with the restrictions >of the high-capacity d/l server, it just ends up not getting used...
Charles, No subdirectory support yet. :-( I've been asking for this for a long time. The SF staff keeps telling me that a rewrite of the file release system is in the works. I agree the SF file release system is lacking in many ways. That's why I'm suggesting cvs for our files, and daily export to the shell server for packages and documentation. >Can you imagine what our SF download page would look like with every >package, disk-image, and utility available...most with multiple versions, >and all listed on a single *HUGE* page? I don't even want to think about the mess that would cause, and I'm not suggesting it. I only want to place releases/branches in the SF file release system. This will be done in the same manner it is done currently. Note: I may tarball pub/packages periodically and place it in the SF files area too. >There are also issues with some of the larger site mirrors (ie my site and >Rick's c0wz site)...it's not exactly easy to migrate an existing site with >a lot of file content to the split SF web/download servers. Maybe some >solutions will present themself as my local SF mirror developes...also, >now that I *CAN* mirror the SF site, I'm more inclined to tweak my local >website to fit SF, even though this will probably mean loosing my existing >mirrors, which are currently expecting static content available via rsync... I'm of the opinion that the lrp.steinkuehler.net mirror/vhost should be exempt from this new policy. It's too large to migrate to the new system easily. However, I am considering archival of c0wz until Rick returns. I'd like to integrate c0wz links into our phpWS weblinks, and place its dox tree in cvs for integration into our HowTo/DocManager-FAQ sections. This is a huge job though, and I haven't even scratched the surface of stuff on my current to-do list. I know these actions are drastic, but we need to do something to control file sprawl. -- Mike Noyes <[EMAIL PROTECTED]> http://sourceforge.net/users/mhnoyes/ http://leaf.sourceforge.net/content.php?menu=1000&page_id=4 _______________________________________________ Leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
