public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Jones <carpaski@twobit.net>
To: gentoo-dev@gentoo.org, gentoo-user@gentoo.org
Subject: [gentoo-dev] Portage-2.0.47-r4 -- Testing
Date: Tue, 25 Feb 2003 05:55:40 -0600	[thread overview]
Message-ID: <20030225055540.A4157@twobit.net> (raw)

Portage-2.0.47-r4 is out for testing. It's masked in package.mask as
always. This one should be ready for public release. Test please and
give me feedback.

This one is mostly cleanups of 2.0.47-r3 and fixes to the changes from
group wheel to group portage. Note that all actions are now preceded by
'--' and are effectively flags.

--NJ

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

25 Feb 2003; Nicholas Jones <carpaski@gentoo.org> *: Update docs and help
to match the deprecation of actions without '--' preceding them.

25 Feb 2003; Nicholas Jones <carpaski@gentoo.org> portage.py: Message
updates. Fix secpass for portage user. Set PORTAGE_GID for ebuild.sh to
use regardless of GID in use (wheel/portage). Only try and delete things
in PORTAGE_TMPDIR if we have perms to do it... see secpass note. Moved the
cachedir creation after settings in created so that we can use spawn instead
of system for the calls to 'chown/chmod -R'. Fix the note on make.defaults.
Fix for the 404 catcher in the fetch code.

25 Feb 2003; Nicholas Jones <carpaski@gentoo.org> emerge: Move all actions
into '--action' form -- Notify of deprecated usages. Moved the functions
from the top of emerge down below the command line parser for readability.
Kill FEATURES=noauto if we're running emerge -- it can break things. Make
-U imply -u so people aren't confused. --debug now enables all debug
variables in portage. Fix wheel/portage group requirements messages. Get
the current portage version when doing rsync via the portage tree's files
and not the loaded cache so that it is aware of changes immediately instead
of the next run. 

25 Feb 2003; Nicholas Jones <carpaski@gentoo.org> ebuild.sh: Try to change
to good a good path at the start of the ebuild to prevent operations from
happening in places like home. After the ebuild's install phase, check to
see if any unsafe perm combo's exist and die if they do. Fix permissions
on the cachedir as we're changing them to root:portage. &> on environment
file prevented it from actually creating the file -- changed to 2>. Change
'true' to 'exit 0' to be a bit more explicit about what we're doing.

24 Feb 2003; Alain Penders <alain@gentoo.org> repoman: Added
nested/sub-shell die testing.

23 Feb 2003; Alain Penders <alain@gentoo.org>: Added bin/portageq tool to
provide access to portage internal information without using APIs that
are changing.  All tools that currently access portage information by
importing portage.py and poking around in it should switch to using this
tool instead. Changed some tools in bin/ to use it, so those won't break
either.

--
gentoo-dev@gentoo.org mailing list


             reply	other threads:[~2003-02-25 12:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-25 11:55 Nick Jones [this message]
2003-02-25 12:30 ` [gentoo-dev] Portage-2.0.47-r4 -- Testing MAL
2003-02-26  3:31 ` Brian Jackson
2003-02-26  9:15   ` [gentoo-dev] Downgrade from gnome 2.2 to gnome 1.4 with emerge -u world? Benjamin Podszun
2003-02-26  9:35     ` [gentoo-dev] emerge rsync Benjamin Podszun
2003-02-26 10:01       ` Gertjan
2003-02-26 10:10       ` c.wegener
2003-02-26 12:01         ` Matt Tucker
2003-02-27 10:24     ` [gentoo-dev] Downgrade from gnome 2.2 to gnome 1.4 with emerge -u world? Spider
2003-02-27 10:35       ` Dar-Klajid
2003-02-27 11:59         ` Spider

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=20030225055540.A4157@twobit.net \
    --to=carpaski@twobit.net \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-user@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