[Planetlab-devel] myplc-devel

[Kevin Atkinson]

On Tue, 4 Jul 2006, Mark Huang wrote:

>> My personal opinion on this matter is that at this stage we do not
>> need a perfectly wrapped nor self-contained packaging. We did not
>> reach the point yet, where we'd need to create a build env as easily
>> as, say, mysql-devel. So a combination of instructions/scripts, in
>> much the same way as pl_box used to work, could probably do the trick.
>
> Okay. Well, here are the basic steps (and options for each step):
>
> 1. Install Fedora Core 4. Two options:
> 	a. In a chroot with yum --installroot, I can provide a script for 
> this.
> 	b. For real with a boot CD/DVD, I can provide a kickstart script for 
> this.
>
> 2. Obtain access to Fedora Core 4 binaries. Two options:
> 	a. Leave everything as is. The build scripts will try the Princeton 
> CS Fedora mirror via FTP, then CoBlitz via HTTP. This could be very slow 
> and/or non-reproducible. It also requires network access.
> 	b. Copy Fedora Core 4 base, extras, and updates to 
> /usr/share/mirrors/fedora from your favorite (or Thierry's, or Princeton's) 
> Fedora Core 4 mirror. I can provide a script for this.

I don't see any reason why you can't easily support both of these.

> 3. Download PlanetLab source code. Two options:
> 	a. Checkout the "build" directory from Princeton. Run "make" inside 
> the "build" directory, which will checkout code from Princeton.
> 	b. Export all source code from Princeton (I can provide the command 
> for this). Import into local repository (can also provide command for this). 
> Checkout "build" from your local repository. Run "make" inside the "build" 
> directory, which will checkout code from your local repository.
>
> Supporting all of these options with a single script could be difficult. I 
> recommend:
>
> 1a -> 2b -> 3b
>
> With a --url option to specify which Fedora Core mirror to use.

That will work for me.  I will have to see the results for more specific 
comments.