linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Bethe <dan_bethe@yahoo.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Auto update
Date: Sun, 19 Mar 2000 19:43:45 -0800 (PST)	[thread overview]
Message-ID: <20000320034345.24572.qmail@web1004.mail.yahoo.com> (raw)


--- "James B. Parker" <pajama1@mindspring.com> wrote:
>
> Is there some sort of auto-update feature in Linux?
> Like some program I can run that checks my currently installed
> package
> versions versus what is available and informs me if a newer version
> exists?
> Or should I just memorize the version of every package I have
> installed?

	Get rpmfind.  You can find it at www.rpmfind.org or
ftp://rpmfind.net/linux/yellowdog/champion-1.2/ppc/YellowDog/RPMS/rpmfind-1.4-2.ppc.rpm
might work.
	Then use the following:

for i in `rpm -qa` ; do rpmfind --latest $i ; done

	That's really quick & dirty  :)
	If anyone thinks that this is a bad idea, perhaps if it is a waste of
global resources, then let us know!  I don't know how
resource-intensive rpmfind is.
	I don't understand why people say that RPM can't do automatic
retrievals and updates.  Usually, people compare it to Debian, saying
that Debian can do that and RPM can't.  You can substitute an ftp or
http URL just as easily as a filename, for any of RPM's operations --
getting info, installing, querying, and more.  And RPM can find them
for you in the first place.

=====
"Don't expect your own messiah; this neverworld which you desire is
only in your mind." -- http://www.dreamtheater.net/songb4.htm#IV5


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2000-03-20  3:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20  3:43 Dan Bethe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-17 19:22 Auto update James B. Parker
2000-03-17 20:06 ` Michael Schmitz
2000-03-17 20:15 ` Stephen Edie

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=20000320034345.24572.qmail@web1004.mail.yahoo.com \
    --to=dan_bethe@yahoo.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 NNTP newsgroup(s).