[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Installers..

#07-Dec-01# Message from *Steve Baker*:
Hi Steve,

> Dunno - I'm a big fan of autoconf/automake.
> A vast percentage of source packages install that way and people are quite
> used to

>   ./configure ; make install
I'm not talking about replacing it - I'm talking about adding a layer
between the user and the scripts. It's fine /for us/, but have you ever sat 
a new linux user in front of a computer with a bunch of tarballs and told 
them that all you need to do is 

make install

I experienced this situation this past weekend with my brother, an 
experienced Windows user (and he built his own computer, so he's no 
technophobe - this guy fiddles registry keys without hesitation) but a 
linux newbie. The results were instructive to say the least. I'm not 
talking about replacing autoconf/automake; for actually handling the 
underlying operation it is fine, but for Harry Homeowner it is hopeless 
(quite apart from it being shell based). When things work it is not bad, 
that I'll grant, but if anything goes wrong - Harry hasn't double-checked 
his dependancies, or he doesn't know how to check that a specific package 
is installed, or he puts things on in the wrong order - it is a nightmare 
for someone who can't decypher esoteric logs. I'm talking about adding a 
layer on top: a GUI similarish to kconfigure but aimed more at the newbie. 

But if you're interested in what I'm up to, I'll post the full description.
It's a sizable read though because I wanted to explain what, how and why I'm
doing things.

 .------{ http://www.starforge.co.uk }-----. .---------------------------.
=[     Explorer2260, Designer and Coder     \=\ P: TexMaker, ROACH, site  \
=[___You_will_obey_your_corporate_masters___]==[ Stack: EETmTmTRRSS------- ]
5. IN ANOTHER OFFICE: After the tea break staff should empty the teapot
and stand upside down on the draining board.