From: Brett Dikeman <brett@arthur.malebolge.com>
To: Jeffrey A Law <law@cygnus.com>
Cc: egcs@cygnus.com
Subject: Re: as problem, PPC
Date: Mon, 03 Nov 1997 02:06:00 -0000 [thread overview]
Message-ID: <v03102805b08327db7650@[144.89.161.9]> (raw)
In-Reply-To: <16680.878539614@hurl.cygnus.com>
At 12:46 AM -0600 on 11/3/97, Jeffrey A Law wrote:
> I suggest you contact whomever sets up the RPM (I assume these are
I spoke with someone who used the same stuff, and he was not able to
identify my problem.
> some kind of "package install" systems?).
sorry, I thought everyone was familiar with RPM's.
Redhat Package Manager
By RedHat.
Basically, a smart, compressed tarball. It can run install/removal
scripts, and checks for dependencies(ie, package less-X.yz needs
libncursesX.zy.)
Comes in two flavors: SRPMs(source RPMs) and RPMs(which usually contain the
compiled, end result.)
RPM is a Linux thing, and [S]RPMs are built by anyone who wants to; there
is no rpm head-hauncho :)
As many have pointed out, posting RPMs made by Joe Shmoe to big sites is
like giving Joe Shmoe root access to hundreds or thousands of systems.
Convenience vs. Security. The age old problem.
Still, I don't understand the message. Oh well. I'll ask the Linux-pmac
group and see what they say.
Brett
------
Brett Dikeman
dikemanb@stu.beloit.edu dikemanb@edison.ma.ultranet.com
~)-|
Hostes alienigeni me abduxerunt. Qui annus est?
Te audire non possum. Musa sapientum fixa est in aure.
------
next prev parent reply other threads:[~1997-11-03 2:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-02 22:27 Brett Dikeman
1997-11-02 22:44 ` Jeffrey A Law
1997-11-03 2:06 ` Brett Dikeman [this message]
1997-11-03 3:21 ` Franz Sirl
1997-11-03 1:33 ` Richard Henderson
1997-11-03 9:43 ` Brett Dikeman
1997-11-03 16:27 ` Elliot Lee
[not found] ` <199711031351.KAA04460@pincoya.inf.utfsm.cl>
1997-11-03 9:43 ` Brett Dikeman
1997-11-03 13:37 ` H.J. Lu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='v03102805b08327db7650@[144.89.161.9]' \
--to=brett@arthur.malebolge.com \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).