Hey,
I think someone asked about this before, and being the dick that I am, I
think I mocked them, but recently I've run into this problem, so I was
wondering what you all thought.
Sometimes I want to know how out RPMs were ./configured, i.e. what
compile-time options were used. Sometimes this is crucial info when
building other packages. Currently I have to download the SRPM, install
it, inspect the spec file, delete the SRPM and cleanup my rpm tree.
This sucks.
Is there any way we could set up a simpler system?
If rpm2html included the spec file, we could get this info from
rpmfind.net, but that's not the case.
Otherwise, maybe we could set up a script that copies the spec file into
a searchable database when it is uploaded to the main/contrib tree.
Or is there a simpler way to do this that I'm missing?
WDYT?
Austin
--
Austin Acton Hon.B.Sc.
Synthetic Organic Chemist, Teaching Assistant
Department of Chemistry, York University, Toronto
MandrakeClub Volunteer (www.mandrakeclub.com)
homepage: www.groundstate.ca
