On Fri, 2 Jun 2006 01:46:09 +0200, Hemmann, Volker Armin wrote:
--deep is dangerous!
I have stopped using --deep ages ago.
As an example:
there is an --deep update for libFOO.1 to libFOO.1.1.
You make this update which only shows up with --deep
Suddenly all apps, linking to
Neil Bothwick wrote:
On Fri, 2 Jun 2006 01:46:09 +0200, Hemmann, Volker Armin wrote:
--deep is dangerous!
I have stopped using --deep ages ago.
As an example:
there is an --deep update for libFOO.1 to libFOO.1.1.
You make this update which only shows up with --deep
Suddenly all apps,
On Friday 02 June 2006 09:48, Neil Bothwick wrote:
--deep is an option, and I understand why you choose not to use it, but
on this occasion it is necessary to accomplish the OP's goal.
and I really do not believe that ;)
If a package is 'hit' by the new flag, --newuse should cover it. With
On Fri, 2 Jun 2006 15:44:46 +0200, Hemmann, Volker Armin wrote:
--deep is an option, and I understand why you choose not to use it,
but on this occasion it is necessary to accomplish the OP's goal.
and I really do not believe that ;)
Believe what you like, I am relating direct experiences
At Fri, 02 Jun 2006 00:29:10 +0100 Neil Bothwick [EMAIL PROTECTED] wrote:
On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote:
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
no you have not:
emerge -a --newuse world
--newuse
On Friday 02 June 2006 16:00, Neil Bothwick wrote:
On Fri, 2 Jun 2006 15:44:46 +0200, Hemmann, Volker Armin wrote:
--deep is an option, and I understand why you choose not to use it,
but on this occasion it is necessary to accomplish the OP's goal.
and I really do not believe that ;)
On Friday 02 June 2006 18:33, Allan Gottlieb wrote:
At Fri, 02 Jun 2006 00:29:10 +0100 Neil Bothwick [EMAIL PROTECTED] wrote:
On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote:
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
no you
On Fri, 02 Jun 2006 12:33:39 -0400, Allan Gottlieb wrote:
Which version of emerge/portage is being discussed?
2.1-rc3
I also don't see an explicit mention that --newuse implies --update
--newuse (-N)
Tells emerge to include installed packages where USE flags
have changed
Hemmann, Volker Armin wrote:
On Friday 02 June 2006 16:00, Neil Bothwick wrote:
On Fri, 2 Jun 2006 15:44:46 +0200, Hemmann, Volker Armin wrote:
--deep is an option, and I understand why you choose not to use it,
but on this occasion it is necessary to accomplish the OP's goal.
At Fri, 02 Jun 2006 17:47:03 +0100 Neil Bothwick [EMAIL PROTECTED] wrote:
On Fri, 02 Jun 2006 12:33:39 -0400, Allan Gottlieb wrote:
Which version of emerge/portage is being discussed?
2.1-rc3
That explains why I didn't see it. Thanks.
allan
--
gentoo-user@gentoo.org mailing list
Anthony E. Caudel wrote:
I was going to switch to nptl (only) but emerge ignored my additions to
make.conf. Then I noticed that my profile is default-linux/x86/no-nptl
so that answers that question.
Can I change my profile to default-linux/x86/2006.0. Any repercussions?
Here is my emerge
On Thursday 01 June 2006 22:43, Anthony E. Caudel wrote:
Anthony E. Caudel wrote:
I was going to switch to nptl (only) but emerge ignored my additions to
make.conf. Then I noticed that my profile is default-linux/x86/no-nptl
so that answers that question.
Can I change my profile to
On Thu, 1 Jun 2006 23:10:36 +0200, Hemmann, Volker Armin wrote:
don't forget to check the useflags (with ufed), and don't forget
emerge --newuse -a world
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
--
Neil Bothwick
This project is so important,
On Thursday 01 June 2006 23:53, Neil Bothwick wrote:
On Thu, 1 Jun 2006 23:10:36 +0200, Hemmann, Volker Armin wrote:
don't forget to check the useflags (with ufed), and don't forget
emerge --newuse -a world
You'll need to add --update --deep to catch packages affected by the
changed USE
On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote:
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
no you have not:
emerge -a --newuse world
--newuse implies --update... adding --update to options.
and I can't remember that this
On Friday 02 June 2006 01:29, Neil Bothwick wrote:
On Fri, 2 Jun 2006 00:48:21 +0200, Hemmann, Volker Armin wrote:
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
no you have not:
emerge -a --newuse world
--newuse implies --update...
Neil Bothwick wrote:
On Thu, 1 Jun 2006 23:10:36 +0200, Hemmann, Volker Armin wrote:
don't forget to check the useflags (with ufed), and don't forget
emerge --newuse -a world
You'll need to add --update --deep to catch packages affected by the
changed USE flags.
Did. Thanks and all is
I was going to switch to nptl (only) but emerge ignored my additions to
make.conf. Then I noticed that my profile is default-linux/x86/no-nptl
so that answers that question.
Can I change my profile to default-linux/x86/2006.0. Any repercussions?
Here is my emerge --info:
Portage 2.0.54-r2
18 matches
Mail list logo
