That frood Paul Lussier sassed:
> In a message dated: Tue, 14 Nov 2000 15:28:42 EST
> Benjamin Scott said:
>
> I disagree with all these design decisions:
[complaints about RPM handling source RPMs SNIPped]
I have to agree with Ben here actually. Using a software package
manager to manage source code just seems awfully silly to me. I'm
inclined to think the only reason those features exist is for RedHat
to automate rebuilding a package to make it easy for their trained
monkeys, and there are already tools that do that.
I can't argue with your points specifically, since given that the
designers of RPM have decided to use it that way, it makes sense to be
able to remove it that way, and even to figure out what version you
have installed (though the time savings here is really minimal so as
to make the argument really silly).
So instead, my argument is that RPM has no business attempting to
manage source code AT ALL. There are already excellent tools to do
that. I'd much rather see RedHat (et. al.) provide a tarball with the
pre-patched source and a proper make file which will build the
software when you type "make" (imagine that?) rather than learn all
this gobbledygook with building the software with RPM. It just makes
no sense.
In most cases, the source RPMS are based on pre-existing packages that
you can (mostly) get off Sunsite (or whatever it's called this week)
so if you really want to see what they changed you can do the diffs
yourself to get the packages.
--
We sometimes catch a window, a glimpse of what's beyond
Was it just imagination stringing us along?
---------------------------------------------------
Derek Martin | Unix/Linux geek
[EMAIL PROTECTED] | GnuPG Key ID: 0x81CFE75D
Retrieve my public key at http://pgp.mit.edu
**********************************************************
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
**********************************************************
