From transami at runbox.com  Sun Aug 15 20:44:32 2004
From: transami at runbox.com (T. Onoma)
Date: Sun Aug 15 20:55:11 2004
Subject: [baker-baker] Status
Message-ID: <200408152044.32756.transami@runbox.com>

For all those interested.

I'm currently tied up with other projects, and won't be able to get back to 
Baker for some time (a few months or so).

In the mean time I've been thinking about sectioning the project into distinct 
sub-projects. The first project will simply be a universal programs meta-info 
repository (the yaml format for which is already pretty much developed) and a 
ruby library for accessing it. Simple.

This means that Build Recipes will be kept in separate files from the 
Meta/Source-Info. While it may seem more complex to have separate files, it 
allows for a variety of Build Recipes per Meta-Source-Info file. Hmm... we 
need a better name than Meta-Source-Info file, perhaps Batter file, or 
Premix?

Anyhow, by dividing this up, we can start in on the first part rather quickly 
and easily make great progress, ready for the second part when the time 
comes.

BTW. With the first, I want to add a bitkeeper sources section.

As for the second part. I am looking at porting relink from Perl to Ruby, 
using Rake if possible, and trying to keep recipes relatively simplistic, a 
la Gobo. (which, for history buffs, is were this all started --long story).

Lastly, the third part of this will be to use Autopackage with Ruby bindings 
for GUI front-end... or create our own.

Oh and I should point out the FHS-Map might branch out on its own too. Seems 
to me that the whole of the Linux community is dying for something like this.

Sound like a plan?

-- 
T.
From transami at runbox.com  Sun Aug 15 23:49:33 2004
From: transami at runbox.com (T. Sawyer)
Date: Sun Aug 15 23:52:40 2004
Subject: [baker-baker] Status
Message-ID: <200408152349.33778.transami@runbox.com>

For all those interested.

I'm currently tied up with other projects, and won't be able to get back to 
Baker for some time (a few months or so).

In the mean time I've been thinking about sectioning the project into distinct 
sub-projects. The first project will simply be a universal programs meta-info 
repository (the yaml format for which is already pretty much developed) and a 
ruby library for accessing it. Simple.

This means that Build Recipes will be kept in separate files from the 
Meta/Source-Info. While it may seem more complex to have separate files, it 
allows for a variety of Build Recipes per Meta-Source-Info file. Hmm... we 
need a better name than Meta-Source-Info file, perhaps Batter file, or 
Premix?

Anyhow, by dividing this up, we can start in on the first part rather quickly 
and easily make great progress, ready for the second part when the time 
comes.

BTW. With the first, I want to add a bitkeeper sources section.

As for the second part. I am looking at porting relink from Perl to Ruby, 
using Rake if possible, and trying to keep recipes relatively simplistic, a 
la Gobo. (which, for history buffs, is were this all started --long story).

Lastly, the third part of this will be to use Autopackage with Ruby bindings 
for GUI front-end... or create our own.

Oh and I should point out the FHS-Map might branch out on its own too. Seems 
to me that the whole of the Linux community is dying for something like this.

Sound like a plan?

-- 
T.