public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Patrick Börjesson" <psycho@rift.ath.cx>
To: gentoo-portage-dev@gentoo.org
Subject: [gentoo-portage-dev] if (world file) then {no add to world when update pkg}
Date: Thu, 11 Dec 2003 19:44:55 +0100	[thread overview]
Message-ID: <20031211194455.18c966bf.psycho@rift.ath.cx> (raw)

[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]

I just thought that if portage-ng is to rely on a world file just as
current portage, then one idea would be to not add the packages you
update manually with 'emerge -u <package name>' to it.
There was a thread in gentoo-user today which took up this matter when
someone asked for a way to update all the packages currently installed
on his machine. One method is to run 'emerge -Du `qpkg -I -nc`', but as
someone pointed out, this would add every single package you have on
your system to your world file (which I guess nobody wants) if you
didn't supply the --oneshot flag to emerge. I propose that the default
behaviour for portage-ng would be to check whether the package you're
trying to update is already installed on the system, else do nothing.
And if it's installed it shouldn't add the package to world after the
merging is completed (which it currently does). 
Would there be some negative sides of doing it this way? And if not, why
is this not default behaviour in current portage?
Feedback (in all its forms) appreciated.

Patrick Börjesson

-- 
Public key ID: 4C5AB0BF
Public key available at wwwkeys.pgp.net

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-12-11 18:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-11 18:44 Patrick Börjesson [this message]
2003-12-11 19:37 ` [gentoo-portage-dev] if (world file) then {no add to world when update pkg} Marius Mauch

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=20031211194455.18c966bf.psycho@rift.ath.cx \
    --to=psycho@rift.ath.cx \
    --cc=gentoo-portage-dev@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