On Sun, 27 Aug 2000, Matt Wilson wrote:
> The right solution:
>
> # rpm -Uvh procps-2.0.7-2.i686.rpm rusers-server-0.17-5.i386.rpm
>
> Something that concerns me about RPM users is that the don't realize
> that they can satisfy co-dependencies by upgrading to packages at
> once. I think we need a good packaging tool to help fix this.
And what is RPM, chopped liver? ... Will your "concern"
motivate you to advocacy within the corporate offices at Red
Hat. Will you get EWT interested again in the 'crown jewel'
which differentiated Red Hat? In finishing it? Polishing it?
All RPM needs is __documentation__: Examples in the RPM
man page, and an updated HOWTO, and a FAQ on the rpm.org
webpages. Automated tools (a new and improved up2date, or
skins for Gnomorpm) _should be_ adjunct wrappers. They are
not where effort needs to be.
Writing documentation is not fun, is preceived as not
'advancing' a product; making changes to code is. The
solution is not another tool -- the solution is to complete
the partially made tools.
The tool is not complete until the 'paperwork' is done. But
if one follows the RPM list, the emphasis is clear --
'someone else' can submit that part - 'patches are welcome'.
- Want to know what the current release is; According to
http://www.rpm.org/, "The current latest release is: 3.0.4"
- Want to know how to build as non-root; better keep you own
archive of the RPM mailing list. The one which "is supposed
to be archived at archives.redhat.com" at:
http://www.rpm.org/mailing_list.html is STILL a dead link.
Oh, that's not fair - check
http://www.redhat.com/mailing-lists/rpm-list/ -- Sure -- _it_
is current to February.
- Have you installed a rawhide rpm-4,x, and want to backtrack
to -3.x; better 'clip and save' a mailing list post, for you
won't find it in the documentation.
- Want to know the best source of documentation; According to
http://www.rpm.org/, "There are several documents on RPM
available. The best of these is Maximum RPM," Sure -- you and
I know better, but what of the newbie coming to RPM?
- Oh, want that rawhide package, X-4.x, built with rpm-4.x;
better be ready to dive into the development pool headfirst.
- Want to use an RPM v.1 packaged product; Not with rpm-4
unless you're a member of the club that is 'in the know.'
- Want to know when a RPM version changes; better refresh
against the CVS, and diff the changelog - It won't show in
changing patch levels.
- Want to understand the RPM macro development plans; can't be
done. The TODO has disappeared from the website, and whatever
development agenda sequence Red Hat is following is going to
follow.
We are nearing the end of the development cycle for the the
next Red Hat release; the release candidates packages are on
the public mirrors. A Red Hat staffer noted on one of the LUG
mailing lists that while Red hat does not announce release
dates, it is straightforward to read a calendar and note the
prior timing of releases.
How happy can Red Hat, and EWT be, reflecting on the total
state of RPM? It shipped with the 'hack' of the website
docs, last time. In shipping it without updated docs again?
--
end
==================================
.-- -... ---.. ... -.- -.--
Copyright (C) 2000 R P Herrold
[EMAIL PROTECTED] NIC: RPH5 (US)
My words are not deathless prose,
but they are mine.
Owl River Company 614 - 221 - 0695
"The World is Open to Linux (tm)"
... Open Source LINUX solutions ...
[EMAIL PROTECTED]
Columbus, OH
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
