Geoffrey Lee wrote:
> > Subject: Re: [Cooker] Idea for new utility
> >
> >
> > I think a utility that would ./configure , make , build rpm,
> > install rpm, is
> > what is needed, that way you can more easily uninstall the
> > program and check
> > dependencies of other programs that might need this program.
> >
> >
>
> i see. but they weren't talking about rpm, just run ./configure make and
> make install. this is not a good idea ..given the packaging methiod is rpm
> for mandrake. i misunderstood their message, that's why i made all the
> references about rpm in the msg.
>
> as i said: i'm hacking rpm builder right now. it seems to work ...there's a
> version up in contrib , 3mdk, but it's a little borken becuase hte origianl
> one didn't have buildroot, and i didn't add it in my patch. i've got an
> updaeted patch (4mdk) here on my hard drive, just waiting for lenny to
> update it. right now my patch is ok, it can bulid a generic spec, with
> description, etc, file list .(it even autogenerates a changelog!!) it's ok
> to build stuff as non-root, etc. really schweet. i'm kind of trying to bring
> the stuff to mandrake compliance because
>
> (1) i once had a desire to build some kind of program that could make rpms
> from source but i'm too lazy to do so
> (2) rpmbuiler is easy to hack because it's tcl
>
> 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.
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.
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!
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 ...
---- FREEDOM ----
Finally,
I apologize to have started this topic.
Serge Lussier.
thanx.
