the launchpad concept

[Steven Michalske]

oops sorry :-P

here is a text copy

hardkrash

On Sunday 22 February 2004 4:09 pm, nestu wrote:
> Steven Michalske wrote:
> > some ideas about lunar's future
> >
> > I wrote this a while back last summer I think  but it food for thought to
> > our current push to Lunar 2
> >
> > hardkrash
>
> Hello, Steven ;)
> Can you please export this to .txt, please? I have no OO,
> nor Staroffice or similar. So I can't read this that w/o
> doubt has to be incredibly interesting :þ
> TIA,
> Jaime.
-------------- next part --------------
Project Launch Pad proposal

This project is to modularize the back end scripts of the moonbase from the rest of lunar and provide for a "standard" script depot for install.

This is like making the moonbase functions in to a library with only calls to the specified functions of the scripts.  The moonbase will in essence become a seperate identity from the rest of the lunar scripts.

The first proposal is to separate out the build script directory from the moonbase.  This will then become what I (hardkrash) have come to call the "launch pad."  The launch pad will be loaded with the build scripts via the moonbase scripts.  The modules will place there dependencies in this same directory.  The directory order will determine the order of build.

.../launch_pad/001/DETAILS
.../launch_pad/002/DETAILS
.../launch_pad/002/BUILD

This launch pad will specify how lunar will build the modules.  This makes all the dependency sorting to leave lin and become part of launch pad generation.

One benefit to this approach is that profiles can become lists of modules to be added to the launch pad instead of dependencies of a fake module.

This also allows for ease of multiple sources for modules, either held, personal, or standard.

By having the launch pad control the build process additional modules can be added to the launchpad as they are built, ie if module_installed then lin xyz.