T. Onoma
11/28/2003 9:41:00 PM
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
5) Creates automatic uninstall scripts
6) Single easy to use interface
7) Plenty more...Want to add a feature? Come over and help.
> > Its commandline interface called 'bake' makes it easy to download,
>
> 'bake' seems very similar to 'rake'. Why not use Rake ?
I've actually been lookong at Rake. I like Rake a lot, but Rake is much more
"general purpose" and ties you into using Ruby itself for package
maintainence. Baker allows you to use shell scripts (most common), ruby
scripts (including Rake), perl scripts, python scripts, etc. Rake I think is
more suited to making actual program installers. 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.
> > compile and install programs. A catalog of "recipes" (also
> > called the "recipe book" can be sync'd with masters and contains yaml
> > files that describe where to get a program (handles mirrors and local
> > regions), how to compile it and how to install it.
>
> 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.
Thanks for asking!
-t0