On Mon, 13 Nov 2000 [EMAIL PROTECTED] wrote:
>> That's one of the really nice things about RPM. You can grab the SRPM and
>> unpack it in one easy motion. You can then examine the spec file to see
>> what ...
>
> This is one of the things where RPM seems to fall short. I can "install" a
> source package, as SRPM, but it doesn't seem to get into the RPM data
> base.
This Is By Design(TM).
RPM takes the stance that the package management database is for installed
and (presumably) working packages.
Source packages are more like user data, as far as RPM is concerned, and an
SRPM is more like a special kind of tar file than an installable package.
Package management doesn't apply. You will find the sources and spec files in
the appropriate locations. The results of building RPMs are completely
package dependent, but will always be in the $RPMSRCDIR/BUILD directory.
"rm" is the only package management command you need.
This might not The Right Thing, but it is the way RPM does things, for
better or worse.
> I can't uninstall it, query it, or use any of the management tools that
> RPM has for binary packages.
How many of those apply, though?
Query? You've got the spec file, which you are presumably interested in,
since you're mucking around with the sources. What are you going to query?
You don't upgrade source packages.
Uninstall? You don't uninstall user data. If you don't want something
anymore, you just delete it.
> I may not be using it right (RH 6.x systems).
I think it is more "intended usage" than "using it right".
--
Ben Scott <[EMAIL PROTECTED]>
Net Technologies, Inc. <http://www.ntisys.com>
Voice: (800)905-3049 x18 Fax: (978)499-7839
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
