public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: <jasonm@indosoft.ca>
To: <gentoo-dev@cvs.gentoo.org>
Subject: [gentoo-dev] emerge --pretend update questions.
Date: Thu Aug 23 11:56:01 2001	[thread overview]
Message-ID: <Pine.LNX.4.33.0108231439140.25758-100000@berkeley.indosoft.unb.ca> (raw)
In-Reply-To: <E15ZySX-0007rR-00@cvs.gentoo.org>

hi,

hopefully this will be my one and only stupid question on this list. :)

i'm trying for a better understanding of the output from:
$emerge --pretend update

when executed on my current system, i see many lines of this:
[ebuild   U] sys-apps/tar-1.13.19-r1 to /
[ebuild   U] sys-apps/sh-utils-2.0j-r4 to /
[ebuild  R ] sys-apps/watchpid-0.1-r1 to /
[ebuild N  ] app-editors/nano-1.0.3-r1 to /
[ebuild  R ] sys-apps/tcp-wrappers-7.6-r2 to /
[ebuild   U] sys-apps/grep-2.4.2-r4 to /
[ebuild  R ] sys-apps/texinfo-4.0-r2 to /
[ebuild  R ] sys-devel/autoconf-2.13-r2 to /
[ebuild  R ] sys-devel/automake-1.4-r2 to /

Q1:  what does the R stand for?  i'm pretty sure i understand N and U, and
my first guess for R would be 'remove'.

lets say i:
$cd /usr/portage/sys-apps/grep
$emerge grep-2.4.2-r4.ebuild
$ebuild /var/db/pkg/sys-apps/grep-2.4.2-r3/grep-2.4.2-r3.ebuild unmerge
$emerge --pretend update | grep grep
[ebuild  R ] sys-apps/grep-2.4.2-r4 to /

Q2: porque?

the answer to Q1 will likely explain Q2, i'm hoping. :)



thanks,
j




       reply	other threads:[~2001-08-23 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E15ZySX-0007rR-00@cvs.gentoo.org>
2001-08-23 11:56 ` jasonm [this message]
2001-08-23 12:34 [gentoo-dev] emerge --pretend update questions Peter Kadau
2001-08-23 12:53 ` Thomas Landmann
2001-08-23 22:34   ` Daniel Robbins
2001-08-23 13:00 ` jasonm
  -- strict thread matches above, loose matches on Subject: below --
2001-08-23 15:48 Peter Kadau
2001-08-23 16:00 Peter Kadau

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=Pine.LNX.4.33.0108231439140.25758-100000@berkeley.indosoft.unb.ca \
    --to=jasonm@indosoft.ca \
    --cc=gentoo-dev@cvs.gentoo.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