Re: new sysinstall

Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx> wrote:
> Well, this is turning out to be a real discussion! It's getting a little
> far-afield, though. Everyone needs to keep in mind that this is for
> building an installation system.
>
> I think we can settle on using a web server model, so lets target:
>
> * Apache
> * Links
>
> Choosing the language is more difficult, but keep in mind that we are
> not trying to create something that will be used for general development,
> only something that will be used to support the installer that any
> developer can work on. One of the main reasons why sysinstall is so
> bad is that virtually nobody other then the original author can do any
> significant work on it, and as a consequence very little development has
> been done on it despite it being an eyesore for years.
fast prototyping should probably be an other aspect considered.
>
> * We need to discuss what kind of XML/package-management infrastructure
> we want to have. e.g. dealing with things like MD5 checksums on
> installed files, including installer or package-managed configuration
> files to detect changes, etc etc.
Also - package relocation. It should be possible to tell if the package is
relocatable and if so take needed actions (but only if it is). And there
is probbaly need to difrferentiate between real relocation and install time
only relocation (in case you are stting up a jail, etc or in general
installing to a different path to where it would be run from).
>
> So lets move the conversation over to what kind of configuration
> topology we want to have that will be in addition to the RCNG/RC.CONF
> system (which we MUST have).
>
> -Matt
> Matthew Dillon
> <dillon@xxxxxxxxxxxxx>
--
Sander
+++ Out of cheese error +++