What happened to pup?
Kyrre Ness Sjobak
kyrre at solution-forge.net
Sun May 22 20:52:41 UTC 2005
søn, 22.05.2005 kl. 21.54 skrev Nicolas Mailhot:
> Kyrre Ness Sjobak a écrit :
> > Which method would you describe to a newbie?
> Well just try to actually document what you propose (nice walkthrough
> with localised screenshots) and we'll laught a bit.
> Been there, done that, gui = documentationsize × 5
> If you had done this kind of work before you wouldn't even be proposing
> to add a license screen, as it adds nothing to the service and is a pain
> to document (like the rest, but the rest at least has some purpose)
> I posted a proposal that does what the user actually wants with minimal
> steps - easy to document and to follow. Alan wrote about how making it
> slightly better. You just pile up screens that won't make the user (or
> your) life any easier.
You mean this?:
The really, really simple-to-use installer is a web page that uses your
browser id to suggest the right repo file to dump into /etc/yum.repos.d
with a short example like :
wget -O /etc/yum.repos.d/adobe.repo url
yum install acrobat-reader
(you can add a .repo gui handler if you like but it'll need to be as
simple as these four lines)
That is basically the same. Only thing is, that i want to push the
responsibility to select the correct distro etc from the webserver to a
special program on the client - as it is easier to do, and more
reliable. Plus, no special config needed on the server (possibly except
running a yum repo). And it works off removable storage.
The licence screen - as i said: make it optional. Make it into a weblink
ala "Licence: <a href="blah blah">Gnu GPL</a>" (and then the licence
name isn't a common name, but the name of an individual object (i don't
know the correct English term for that, sorry) - and doesn't need to be
You could possibly squeeze the installer into three, standard screens
(followed by *every* installer, as the .install is just a bunch of
metadata presented by the universal-gui-installer-frontend) (something i
actually mentioned in the first mail, albeit probably not clear enough)
More information about the devel