Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Mike Frysinger <vapier@g.o>
Subject: Re: restricting phases where enew{user,group} is allowed
Date: Sat, 26 Nov 2011 01:42:31 -0500
On Wednesday 23 November 2011 19:31:11 Mike Frysinger wrote:
> currently we blacklist certain phases (which is largely based on EAPI=0 and
> blocking src_*) for enew{user,group}.  moving forward, ferringb suggested
> we invert this into a whitelist of allowed phases.
> 
> afaict, the blacklisting + dev documentation has done a good job of
> restricting calls to three places: pkg_{setup,preinst,postinst}.  so
> inverting the logic should largely be safe.  on the off chance it isn't, i
> think letting the ebuild `die` and getting it fixed up via bug reports is
> acceptable (i grepped through the tree a bit and looked sane).

committed:
http://sources.gentoo.org/eclass/user.eclass?r1=1.10&r2=1.11
-mike
Attachment:
signature.asc (This is a digitally signed message part.)
References:
restricting phases where enew{user,group} is allowed
-- Mike Frysinger
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: restricting phases where enew{user,group} is allowed
Next by thread:
Packages up for grabs due rbu retirement
Previous by date:
Re: making the stable tree more up-to-date
Next by date:
RFC: Gentoo News file about GNOME 3.2's unmasking


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.