On Tue, 15 Jan 2013, Shad L. Lords wrote: > On Mon, Jan 14, 2013 at 5:46 PM, Charlie Brady wrote: > > > > We could use something much more lightweight. But the tools in > > > place make it very easy to build packages without having to worry > > > about having the right environment. Developers just need to commit > > > changes and submit a build request. Everything else happens > > > automatically. > > > > To build packages, maybe. But isos aren't built automatically. Your WIP > > isos build and distribution process using jigdo on the client side > > requires a lot of unnecessary client end storage. I haven't looked at the > > fedora iso build process in a long time - do you still need root to update > > anaconda? > > To build the ISOs I just need to run two scripts.
Yes, *you* do. So that's a bottleneck. > One to rebuild installer with branding/updated packages and one to > compose the ISO, calculate checksums and build the jigdo files. The > main reason I use jigdo to distribute the WIP ISOs is to save on the > bandwidth coming out of my location. Would zsync or rsync not save the same bandwidth? > If we had unlimited and unmetered bandwidth then it would be > easy enough to have a daily ISO automatically built and available for > everyone. Understood. But I don't think jigdo is the right solution. > There are still parts of rebuilding anaconda that need root or > sudo access but this isn't a problem if the scripts are written the correct > way. In what way isn't it a problem? > I'm not saying I've had a perfect track record with the hosting I've done. > But, the amount of time due to hacks or breaches I feel has been > significantly less then it would have been had the system remained on a > single host as it was before I took it over. Yep, no doubt about that. _______________________________________________ Discussion about project organisation and overall direction To unsubscribe, e-mail [email protected] Searchable archive at http://lists.contribs.org/mailman/public/discussion/
