From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Sun, 16 May 2010 21:14:30 -0700 Message-ID: From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] package system for Plan 9: alpha! Topicbox-Message-UUID: 263fe0a8-ead6-11e9-9d60-3106f5b1d025 On Sun, May 16, 2010 at 6:47 PM, Akshat Kumar wrote: > On 5/16/10, ron minnich wrote: >> Between this package tool and mercurial for sources, I don't expect to >> ever need to run replica again. > > How do you plan to keep up with updates > to contrib repos people keep on sources? the BUILD tool rebuilds it all on demand. > Will the contrib -> iso.bz2 conversion take > place on a nightly basis? Some sort of > keeping tabs on modification times? it's actually reasonably fast, rebuilding all the files for all the packages takes < 10 minutes, and that's without any parallelism in the creation ... so it's not a big deal to rerun this every night. Total size of a tar transfer is 500 mbytes or so, and when I use rx that also is done quickly. > > Perhaps it would be nice if people with > contrib repos could themselves make the > ISOs and upload to 9grid or put it wherever > the central iso.bz2 repo will be. Yes, if we decide we like this format we can do that. The build tool does deal with ambiguities and issues: - contrib names things as name/package or package (well people do), which I have to handle. - Also, people mix one or more projects in their root/ directories, so I use the replica/package/proto files to build the .iso.bz2. Really, if people do no more than what they do now, that's fine for me to keep building this set of files. It's really just a script. So I run a script to keep the bitbucket sysfromiso repo up to date, usually daily, and I can do that with this script as well. ron