"Mike A. Harris" wrote:
> I think I see the problem more properly now. You want the .spec
> file from a particular .src.rpm package, and you don't want to
> have to download that entire package. That makes sense. Putting
> it in the binary RPMS for your installed programs is NOT the
> correct solution. Getting someone to write a script to take out
> all of the .spec files for Red Hat and put THEM into a directory
> for download is a FANTASTIC idea. That way you only download the
> .spec file, which is what you want.
there are many packages (eg. gcc) which has many compile time configuration
options and you usualy don't know it without look into the spec file.
and these information is one kind of documentation so the _user_ may
have to need it (not just the rpm builder).
> Or better yet, take all the .spec's and put them in one big
> tarball to download, or heck - even an RPM.
>
> rpm -ivh specs-6.2.i386.rpm
>
> THAT is the way to do it. You get the specs if you want them,
> nobody else has junk on their disks.
it's not just about the distribution there are meny rpm for powertools,
from rawhide, from other sources...
> Really though... trust me... get Maximum RPM.
I've made rpms since rh 3.0 days:-) and already read it, but it seems to
me you don't understand that it not just about make an rpm, rather
use a program which actualy put into an rpm package, and the info
about how this package was build inside the spec file.
-- Levente
"The only thing worse than not knowing the truth is
ruining the bliss of ignorance."
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
