On Sep 13, 2009, at 8:41 PM, Andreas Rottmann wrote:
Hi!
I've just pushed the code of dorodango to
<http://gitorious.org/dorodango>. It isn't useful yet, in particuliar,
the following features are missing from what I want in a first
release:
- Dependency managment
- HTTP support
- ZIP file support
I'll tackle dependency management next, probably by porting aptitude's
resolver algorithm; HTTP and ZIP file support should be relatively
easy
to add; the hooks to do so are in place.
Great! This all looks very good.
For what it can do ATM:
- Scan bundles (which are just directories, until ZIP support is
added).
This mostly involves creating an "inventory" for each supported
category; there is mostly one category I'll care about for now:
"libraries", containg R6RS library files. The package inventories
each
map an hierarchical namespace to files in the bundle.
Categories may be "libraries", "documentation", "programs", and the
like, right? Or do you mean something else?
If a bundle is a set of packages, and each package contains a set
of files, how do categories fit in?
Maybe I also need to know what bundles are really for. (e.g., why
not only packages that have categorized files?)
- Install individual packages contained in a bundle into a destination
which is managed by a package database. The database keeps track of
the pathname to package mapping and is able to detect file conflicts
between packages.
Good.
- The package database is designed to keep track of not only installed
packages, but packages available from repositories as well; on top of
that data, "smart" dependency resolution can be implemented.
Good. (whatever "smart" may mean)
- Destinations can specify how a (package, category, inventory-path)
triple is mapped to a pathname.
There should be some sensible default setting here, otherwise, it
may be too complex for starters.
- Remove a package from the database (and corresponding destination).
Good.
Thanks for the heads-up and for taking the time to work on this.
Aziz,,,
