xml structures and some notes
gerard at linuxfromscratch.org
Wed Sep 6 20:17:31 PDT 2000
> I suppose you are right, and I like the sound of it.
> I see some problems though.
> I don't have the expirience, but is every option changeble and if so,
yes preferably. I want to be very flexible, to the extreme if the user wishes.
> in what parameters. And even more important,
> what options make sense to change?
> When does it make sense to do changes throughout the profile, some
> What about dependencies?
> In short, the Frontend should help the User to save work and/or make it
> (to understand). Otherwise, you could use a text editor.
> IMO there should be a way for the Profile Maintainer to pass that
> information to the Frontend/User.
> But I suppose that an Input tag is realy unessesary for that prupose,
> I like the idea of a <description> Tag like Thomas suggested.
> Furthermore something like a <dependesOn>/<IsNeededBy> would help, but
> I don't know if such a thing is managable (perhabs as a database?)
It's managable. If not, it has to be. You need to satisfy dependenies if you
install a package. You can't get away with not doing dependency checks.
-*- If Linux doesn't have the solution, you have the wrong problem -*-
More information about the alfs-discuss