From: Simon Strandgaard <neoneye@...>
Date: 2003-11-29T07:12:12+09:00
Subject: Re: Baker

On Sat, 29 Nov 2003 06:41:23 +0900, T. Onoma wrote:

> On Friday 28 November 2003 08:07 pm, Simon Strandgaard wrote:
>> On Fri, 28 Nov 2003 15:37:12 +0900, T. Onoma wrote:
>> > Baker is an advanced source-based package management system It is 100%
>> > well structed OO Ruby code, which can easily be extended and called upon
>> > as a library.
>>
>> I think there already exists a project with similar goals.. Rubyx.
>> How are Baker different?
> 
> in fact i talked to Adnrew about rubyx a good bit before strating Baker, and 
> looked over his code in detail. Indeed I had started out with the idea of 
> just imporving rubyx, but Andrew and I had very different ideas. he wanted to 
> keep rubyx as a single all in one program. So Baker was born. I should also 
> mention that at first this was trageted for GoboLinux. But as soon as I told 
> them about what I was thinking the main guy over there turned around created 
> his own shell script sort of thing (Gobo only). Too bad b/c Baker is going 
> way beyond all that have come before. Why?
> 
>   1) Uses 100% OO Ruby
>   2) Uses Yaml
>   3) 100% distro independent
>       (You can use it on any distro. It plays nice even
>        if your FHS is upside down and turned around.)
>   4) Doesn't require a package database

How does this works?  not having a central/homedir database how?


>   5) Creates automatic uninstall scripts
>   6) Single easy to use interface
>   7) Plenty more...Want to add a feature? Come over and help.

Its rarely that I install via source. When I do I use gnu-stow and install
it in my homedir. My machine is slow, not suited for big compile-runs.
Have you considered also distributing binary-packages ?

Even though, it sounds promising.. 
 

>> 'bake' seems very similar to 'rake'.  Why not use Rake ?
[snip]
> Baker is a meta-builder/
> installer, if you will. It organizines the whole process of downloading, 
> compiling, installing, and building distro(s), even allowing you to maintain 
> seperate architecture builds.  But unlike rubyx it extends.

OK.

 

>> Where does it download this information from?   Gentoo?  Bakery?
>> Are there a central repository?  is it distibuted over multiple-servers?
> 
> We're just getting started on creating repositories. So that is yet to come. 
> 
> Anyone is welcome to help, from developement to simple recipe testing.

I have been involved in an operating-system project some years ago.
We collected many nice ideas. Many documents are unfortunatly in danish,
but there are some in english.  You can browse them here:
http://cvs.sourceforge.net/viewcvs.py/metasystem/text/uk/cryos/dos/
Please tell me what you think.

I would like to help if the project goals were like the visions of the
above project :-)

How does the package-category system work ?


--
Simon Strandgaard