From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Portage 1.6.7 released
Date: Wed Sep 5 00:47:02 2001 [thread overview]
Message-ID: <20010905004639.B23173@cvs.gentoo.org> (raw)
Hi All,
A new version of Portage (1.6.7) is now on CVS. Here's the ChangeLog:
Portage 1.6.7, released 05 Sep 2001
===================================
*portage.py
(last-minute fix)
CONFIG_PROTECT unmerge protection is now observed for symlinks, fifos and
device nodes.
*portage.py
Fixes for unmerging CONFIG_PROTECTed files. Protected files are now *not*
unlinked from the filesystem. Messier but safer, and simplifies package
upgrades.
*emerge
Emerge output cleanups for GNU info directory generation. New --verbose
mode; new CONFIG_PROTECT scanning feature to let people know when there are
config files to be updated. New "--help config" docs to explain how to
do it.
Portage 1.6.6, released 01 Sep 2001
====================================
*portage.py
Upgraded directory merging over existing objects. Existing symlinks that
point to existing directories will be kept and used as is; directories will
be used as-is; any other objects (broken symlinks, files) will be copied
to origfilename.backup and a ne directory will be created in its place.
Portage 1.6.5, released 31 Aug 2001
====================================
*emerge
Fixes for handling multiple ebuilds, packages and/or dependencies on
the command-line.
*portage.py
An optimization to the digraph class so that the firstzero() method finds
matches in close to the order that keys were added to the digraph.
--
Daniel Robbins <drobbins@gentoo.org>
Chief Architect/President http://www.gentoo.org
Gentoo Technologies, Inc.
reply other threads:[~2001-09-05 6:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20010905004639.B23173@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-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