> >
> > rpm builder has been hacked heavily ... prob need some ppl to
> test for me.
>
> Ok then,
> Let say that its a bit complicated and there is
> already a work making its way...
>
> However, It seems to be an interresting point :-)
> I am sure something could be done.
>
yop
> For myself:
> All this mean that right now I better start to learn how to make
> RPM packages if I want to contribute :-)))
>
> Yes, I agree about RPMs way.
>
the mdk rpmhowto is a little outdated now, hopefully a new one will be out
soon :)
> Civilem says:
>
> > I think it is a safe bet to say that there is almost always a
> > file in the package called info or readme or install which can be
> > parsed for package-specific instructions. Perl or Python have
> > some ready-written parsers which should usually(tm) be able to
> > extract the install instructions and standardize the language so
> > that a routine could pick them up and perform the amazing feats
> > of legerdermain required to make an install.
>
> ("legerdermain" ?)
>
> - Yes, but imagine a huge package ( let say netscape )
> which has so much files, scripts. etc ...
> it could be impossible to parse the configs setup!
>
>
netscape only comes in binary, you see.
> no,no,no ....
> I just wanted to suggest to give the choice of an alternative
> installer/uninstaller for non existant RPM-built sources,
> or if I prefer not to go RPM way for that specific software ...
the biggest problem is that because of all the different way the Makefile
behaves it's realy hard to make okne which can work for ALL packages, plsu
some packages don't run through configure e.g. documentation. i can make one
which should work for almost anything, but not all. e.g. samba puts its
configure in the source directory.
so you would have to untar the source , and tehn cd to samba-2.0.7, and then
cd to source, and then run ./configure ..
> ---- FREEDOM ----
>
>
> Finally,
> I apologize to have started this topic.
>
> Serge Lussier.
>
> thanx.
>
