My concept of LFS installer

On these hollidays I'll try to write LFS installer. My
vision of this
installer is:
1)Installer will be written in C or C++
2)Installer will parse xml sources of book's. First will be
implemented
LFS and BLFS. Later can be added CLFS and HLFS. This parsed
text will be
saved in /var/something as plain text-user can edit this
text. In this
text will be informations of sites, from which can be
sources
downloaded. When this fails, then sources of program will be
downloaded
from LFS sites. Next this text will include dependncies of
packages and
instructions for package compiling. The dependencies can be
saved in
Berkeley DB too.
3)Every package will have single file in
/var/something/package.
Packages will be logged too for possibility of
uninstallation as in
paco.
4)From packages can be maked precompiled archives
package.tbz for
possibility of installation on another PC. With this
archives will be
included firsboot program for configuring another PC.
5)Installer will use text mode with ncurses and graphical
mode with gtk+
or qt-what is better qt or gtk+?
6)Remote installation will be done with VNC for graphical
version and
ssh for text version.
7)In installer can user set which prefix he want for some
programs as
Qt,KDE,GNOME,X.org,GCC and optimalization.
8)Installer can have option to copy LiveCD to 500MB HDD
partion and when
will be liveCD copied to disk, then can user use Suspend to
disk option,
because compilation LFS and BLFS is quite long. With
suspeding user
don't must configure liveCD systém again and again, when he
stopped work
with LFS. Only resume liveCD systém from disk will suffice.
9)In installer will be included editor of instructions for
installing
packages.
10)In future can be added option's for updating LFS systém
and
installing packages which is not included in BLFS, because
of clear text
version of package instructions. Or installer can logg
process of
instalation and can generate installation instructions
automaticaly?
This instruction of packages that are not in LFS can be in
new project
Extras(The BLFS book don't need to have still new and new
packages).

How far I'm from your idea of LFS installer? Can be my
installer
included as part of ALFS, what's your opinion? I'll try to
start with
programming during July.

Filip Bartmann

-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page

	Hi!
	I have an plan to an sort of alfs tool too.
	My goal is to write a plugin enabled system in c++ that
will build the 
packages according to user needs. So..
A plugin for parse a build file like a .spec or ebuild maybe
in xml extracted 
from the book,  another plugin to download sources and
patches, another to 
solve dependencies and propose changes to fit user needs, 
another for 
packaging... and so on. Maybe one to configure installed
software (this one 
would be great)
	This way, i need to define a common interface for each
task, but the 
internals can be changed inside the plugins.

	By now, I am working on a xml enabled layer to read and
save data. A sort of 
object2xml model. I already tried to reinvent the weel and
write a simple xml 
parser, but by now I think that using libxml or libxml2 can
be better.

	This kind of work is a grreat challange, so I wish you good
luck. If you came 
out with some good working code, people will be like to join
and help you I 
think.


Carlos Eduardo
-- 
Fortune finishes the great quotations, #17

	"This bud of love, by summer's ripening breath,
	May prove a beauteous flower when next we meet."
	Juliet, this bud's for you.
-- 
http://linuxfromscratch.org/mailman/listinfo/alfs-discu
ss
FAQ: http://www.linux
fromscratch.org/faq/
Unsubscribe: See the above information page