[Helidelinux-devel] the structure of lfsbuilder

[Hui Z. <zh...@wa...>]

I restructured my lfsbuilder into different modules.

LFS::Logger takes care of logging during installation or
uninstallation. It optionally logs to file in tabbed format,
it logs to console in colored format, and it supports any number of
logging, can accept tty names to output info in different terminals.

LFS::Fetcher (just a name sofar) takes care of looking for packages
both from local storage and internet. It accepts a package name and a
optional method (such as cvs, latest, version, etc) try to work out
with its intelligence(heuristic) and internet if it's availaible. It
always checks a profile if it exists so one teach it for some odd
package and possible package name translation.

LFS::Pkgger (I am working on it) is the package manager. Works
together with install-log, logs all the installed package status

LFS::Builder controls all other modules and does the actuall
installation, uninstallation, and may be experimenting (Not much idea
yet, sort of construt a pseudo environment and drop into a shell-like
interface do semi-interactive building). It uses a profile(s), but
it not found in the profile, it tries its intelligence (such as try
configure, try make all, try perl *PL, etc), and do certain
analysis(such as analyse the configure script, Makefile, error
messages). --Maybe I should break this into further modules.


LFS::Logger, Fetcher, Pkgger are independent, which mean can be used
individually by another program. The Builder works with all the other
modules.

-Hui