as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
existing stable users wont be affected as the 2.0.x versions will continue to
carry support for this, but some of you stable users may notice some USE
flags suddenly disappearing
Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
existing stable users wont be affected as the 2.0.x versions will continue to
carry support for this, but some of you stable users may notice some USE
On Fri, Jan 13, 2006 at 06:57:24AM -0500, Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
existing stable users wont be affected as the 2.0.x versions will continue to
carry support for this, but some
On Friday 13 January 2006 11:15, Kalin KOZHUHAROV wrote:
Or is it because I always had:
USE=-* ${MY_USE}
in /etc/make.conf?
yes
-mike
--
gentoo-dev@gentoo.org mailing list
On Fri, Jan 13, 2006 at 06:57:24AM -0500, Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
Could you add a USE_ORDER without auto to /etc/make.globals for that
release, please, or alternatively provide some
Can we get this on the website/announce? I agree that auto-use is the
suck and that it needs to die a long excrutiating death, but I think a
lot of users will be like wtf when 2.1 hits stable and --newuse turns up
a massive crapload of packages.
Whether this announced now, or when
On Fri, 2006-01-13 at 06:57 -0500, Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release, we're
looking to cut out use.defaults support
I see this as a good and bad thing. Good in one hand that less autojunk
would be enabled like python/perl bindings not
On Fri, 13 Jan 2006 15:13:02 -0500 solar [EMAIL PROTECTED] wrote:
| The autouse itself is not a bad feature or idea if it were used properly.
| Problem is that it's not been used properly.
No, it's bad. It's another thing that makes correct dependency
resolution impossible.
--
Ciaran McCreesh :
On Friday 13 January 2006 15:13, solar wrote:
On Fri, 2006-01-13 at 06:57 -0500, Mike Frysinger wrote:
as one of the new sane features of the next portage-2.1_pre release,
we're looking to cut out use.defaults support
I see this as a good and bad thing. Good in one hand that less autojunk
