alexander volovics wrote:
> For an average linux user of average ability with NO programming knowledge
> and skills a more realistic, and probably optimistic, estimate would be two
> to three weeks.
>
I see what you guys are getting at here,but how do you jugde average !!
I do quite alot of bash scripting,and am trying to learn perl.
Have used linux for three years now.
> For somebody without programming experience Donny's RPM-HOWTO will probably
> be too terse and without enough examples. The Maximum RPM book is excellent
> but reading AND digesting the relevant portions alone will take about a week.
Its taken me four days to get a working rpm binary(and this is only a
very
simple one),built an rxvt with pixmap support.
Yes i know i could have done it the way i have always done it,but i
wanted to learn.
The how-to doesn`t really explain the process correctly,or at least,it
doesn`t read that way
to me.
the %files section is what ultimatly builds the binary rpm,but i didn`t
realise that it builds
from the files its just installed.This seems wrong to me,installing
files,then building the rpm,to install.A better way must be to create a
virtual install routine,then build the rpm.
Although i have to say that nothing gets installed unless i get a clean
build.
I guess that now i`ve built one,it`ll get easier.(Perl5 here we go).
> Looking at SRPM's is surely to be recommended but for grasping what is
> actually happening and why I would recommend the Maximum RPM book.
> (and of course a lot of trial and error).
>
H`mm this helped but some contain very complex *.spec files.
Maximum RPM is superb,again complex,but when you get to a certain level
of understanding,its immensly useful.
--
Myfish.
Email [EMAIL PROTECTED]
0 0
o
`---'
-
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archiv at http://www.suse.com/Mailinglists/suse-linux-e/index.html
