At 16:24 Uhr +0100 16.03.2005, Frederico Muñoz wrote:
Well, it will be able to install them trough
bundles, but an entire system is a different
beast than individual packages... I think it
would be better to leave the OS installtion to
regular CLI tools, and only use Installer to set
GNUstep, i.e. not glibc and base-utils...
Well, it depends on what the end product is
desired to be. GNUstep Libraries won't even need
an application installer. GNUstep Desktop would
need only an installer for applications. I guess
a complete GNUstep OS (ala LinuxStep) would want
to have a complete GNUstep-like installer from
the start, though.
They could probably just go with the Live CD
approach... Put a minimal GNUstep system on the
CD (probably even without GWorkspace and all
that, launching directly into the installer),
make that install a basic Linux distro with
everything Installer.app wouldn't be able to
manage, then boot into that drive and perform the
rest of the installation using Installer.app
running under GNUstep libs. So, as long as
Installer.app is designed so it can install Unix
packages on another drive, I'd say you needn't
bother with an installer-lib.
Forget I ever mentioned it :-)
Well, the last time I thought about this (using
Installer not only to install add-ons, but
GNUstep proper) it came to mind the idea of
having a statically compiled Installer.app (that
would be much bigger in size) that would be used
to install GNUstep, and would also install the
"regular" Installer.app, removing itself in the
end.
That's basically what I meant by "GNUstep light".
I don't know if this is possible though, but it
would be much better than to write a C wrapper
for it... I think it's important to use GNUstep
from the begining.
Yes, it'd probably also make things easier.
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de
