Re: [gentoo-user] Change profile

2006-06-02 Thread Neil Bothwick
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 libFOO.1 are dead or crashy or acting
 weired.

Dropping --deep won't stop that happening, only delay it. sooner or
later, one of your packages will need libFOO.1.1 and it will be
installed. --deep doesn't cause this problem, it only affects the timing.

 That happened to me several times. I see NO reason to use deep. Ever.

How about this instance? The OP wants all packages affected by the
profile change to be updated. Without --deep, that won't happen.

 Reduced the occurences where I have to use revdep-rebuilt to almost nil 
 (except that expat tragedy some weeks ago. Man that sucked ;) ).

I do a deep update every day, on various architectures. I run
revdep-rebuild -p occasionally, just to make sure everything is
consistent, it rarely picks up anything.

--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.


-- 
Neil Bothwick

Machine-independent: Does not run on any existing machine.


signature.asc
Description: PGP signature


Re: [gentoo-user] Change profile

2006-06-02 Thread Teresa and Dale
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, linking to libFOO.1 are dead or crashy or acting
weired.



Dropping --deep won't stop that happening, only delay it. sooner or
later, one of your packages will need libFOO.1.1 and it will be
installed. --deep doesn't cause this problem, it only affects the timing.
  


Yep.

  

That happened to me several times. I see NO reason to use deep. Ever.



How about this instance? The OP wants all packages affected by the
profile change to be updated. Without --deep, that won't happen.
  


Yep here too.

  

Reduced the occurences where I have to use revdep-rebuilt to almost nil 
(except that expat tragedy some weeks ago. Man that sucked ;) ).



I do a deep update every day, on various architectures. I run
revdep-rebuild -p occasionally, just to make sure everything is
consistent, it rarely picks up anything.
  


I do the same thing.  That is one reason it is there, to fix things like
this.

--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.

  


Yep.  Sometimes you have to do it just because you got to.

Dale
:-) :-) :-)
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Hemmann, Volker Armin
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 or 
without --deep- 
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Neil Bothwick
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 here. Faith has
nothing to do with it.

 
 If a package is 'hit' by the new flag, --newuse should cover it. With
 or without --deep- 

When run with --update only, emerge considers only those packages listed
in world and their direct dependencies. Lower level dependencies won't be
looked at, so portage won;t pick up the changed USE flag.

From the man page

--deep (-D) 

When used in conjunction with --update, this flag forces emerge to
consider the entire dependency tree of packages, instead of checking only
the immediate dependencies of the packages. As an example, this catches
updates in libraries that are not directly listed in the dependencies of
a package.


-- 
Neil Bothwick

Did you sleep well? No, I made a couple of mistakes.


signature.asc
Description: PGP signature


Re: [gentoo-user] Change profile

2006-06-02 Thread Allan Gottlieb
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 implies --update... adding --update to options.
 
 and I can't remember that this was different in the past.

 Yes it was. Adding --update pulled in extra packages, even though they
 were the same version as installed. This was somewhat counter-intuitive,
 so the new behaviour makes more sense. You should still need --deep
 though.

Which version of emerge/portage is being discussed?  I am running
portage-2.0.54-r2.  The man page for emerge suggests (but does not
state) that --update is still needed.

  --update (-u)

Updates packages to the best version available, which may not
always be the highest version number due to masking for
testing and development.  This will also update direct
dependencies which may not be what you want.  In general, use
this option only in combination with the world or system
target.

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 since compilation.  An asterisk marks when a USE
flag has changed since the package was compiled.

Thanks in advance for the clarification and also a general thank you
for your high-quality contributions to the newsgroup.

allan
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Hemmann, Volker Armin
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 ;)

 Believe what you like, I am relating direct experiences here. Faith has
 nothing to do with it.

  If a package is 'hit' by the new flag, --newuse should cover it. With
  or without --deep-

 When run with --update only, emerge considers only those packages listed
 in world and their direct dependencies. Lower level dependencies won't be
 looked at, so portage won;t pick up the changed USE flag.

 From the man page

 --deep (-D)

 When used in conjunction with --update, this flag forces emerge to
 consider the entire dependency tree of packages, instead of checking only
 the immediate dependencies of the packages. As an example, this catches
 updates in libraries that are not directly listed in the dependencies of
 a package.

UPDATES

not NEWUSE

also from man emerge:
 --newuse (-N)
  Tells emerge to include installed packages where USE flags  have
  changed  since  compilation.   An asterisk marks when a USE flag
  has changed since the package was compiled.


and I have seen 'far away' dependencies, that got rebuild, without deep!
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Hemmann, Volker Armin
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 have not:
 
  emerge -a --newuse world
 
   --newuse implies --update... adding --update to options.
 
  and I can't remember that this was different in the past.
 
  Yes it was. Adding --update pulled in extra packages, even though they
  were the same version as installed. This was somewhat counter-intuitive,
  so the new behaviour makes more sense. You should still need --deep
  though.

 Which version of emerge/portage is being discussed?  I am running
 portage-2.0.54-r2.  The man page for emerge suggests (but does not
 state) that --update is still needed.

   --update (-u)

   Updates packages to the best version available, which may not
   always be the highest version number due to masking for
   testing and development.  This will also update direct
   dependencies which may not be what you want.  In general, use
   this option only in combination with the world or system
   target.

 I also don't see an explicit mention that --newuse implies --update

it is not in the manpage, but emerge tells it:
emerge -pN world
 --newuse implies --update... adding --update to options.

These are the packages that would be merged, in order:

Calculating world dependencies
.
.
.

-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Neil Bothwick
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 since compilation.  An asterisk marks when a USE
   flag has changed since the package was compiled.

The man page hasn't changed in this respect, but emerge --newuse informs
you that it will add --update for you.


-- 
Neil Bothwick

Windows '96 artificial intelligence: Unable to FORMAT A: Having a go at C:


signature.asc
Description: PGP signature


Re: [gentoo-user] Change profile

2006-06-02 Thread Teresa and Dale
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.


and I really do not believe that ;)
  

Believe what you like, I am relating direct experiences here. Faith has
nothing to do with it.



If a package is 'hit' by the new flag, --newuse should cover it. With
or without --deep-
  

When run with --update only, emerge considers only those packages listed
in world and their direct dependencies. Lower level dependencies won't be
looked at, so portage won;t pick up the changed USE flag.

From the man page

--deep (-D)

When used in conjunction with --update, this flag forces emerge to
consider the entire dependency tree of packages, instead of checking only
the immediate dependencies of the packages. As an example, this catches
updates in libraries that are not directly listed in the dependencies of
a package.



UPDATES

not NEWUSE

also from man emerge:
 --newuse (-N)
  Tells emerge to include installed packages where USE flags  have
  changed  since  compilation.   An asterisk marks when a USE flag
  has changed since the package was compiled.


and I have seen 'far away' dependencies, that got rebuild, without deep!
  


It seems me and Neil has seen times where it didn't.  I have used -D
several times and it has not caused me any problems. 

Dale
:-) :-)
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-02 Thread Allan Gottlieb
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



Re: [gentoo-user] Change profile

2006-06-01 Thread Anthony E. Caudel

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 --info:

Portage 2.0.54-r2 (default-linux/x86/no-nptl, gcc-3.4.6, glibc-2.3.6-r3, 
2.6.16-gentoo-r7 i686)

=
System uname: 2.6.16-gentoo-r7 i686 AMD Athlon(tm) 64 X2 Dual Core 
Processor 4200+

Gentoo Base System version 1.6.14
dev-lang/python: 2.4.2

snip

Never mind.  I made a backup and went and changed the profile, switched 
to nptl and nptlonly.  No repercussions so far.


Tony

--
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
   -- Benjamin Franklin
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-01 Thread Hemmann, Volker Armin
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 default-linux/x86/2006.0.  Any repercussions?
 
  Here is my emerge --info:
 
  Portage 2.0.54-r2 (default-linux/x86/no-nptl, gcc-3.4.6, glibc-2.3.6-r3,
  2.6.16-gentoo-r7 i686)
  =
  System uname: 2.6.16-gentoo-r7 i686 AMD Athlon(tm) 64 X2 Dual Core
  Processor 4200+
  Gentoo Base System version 1.6.14
  dev-lang/python: 2.4.2

 snip

 Never mind.  I made a backup and went and changed the profile, switched
 to nptl and nptlonly.  No repercussions so far.


don't forget to check the useflags (with ufed), and don't forget 
emerge --newuse -a world
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-01 Thread Neil Bothwick
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, we can't let things that are more
important interfere with it.


signature.asc
Description: PGP signature


Re: [gentoo-user] Change profile

2006-06-01 Thread Hemmann, Volker Armin
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 flags.

no you have not:

emerge -a --newuse world
 --newuse implies --update... adding --update to options.

and I can't remember that this was different in the past.
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-01 Thread Neil Bothwick
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 was different in the past.

Yes it was. Adding --update pulled in extra packages, even though they
were the same version as installed. This was somewhat counter-intuitive,
so the new behaviour makes more sense. You should still need --deep
though.


-- 
Neil Bothwick

The best antiques are old friends.


signature.asc
Description: PGP signature


Re: [gentoo-user] Change profile

2006-06-01 Thread Hemmann, Volker Armin
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... adding --update to options.
 
  and I can't remember that this was different in the past.

 Yes it was. Adding --update pulled in extra packages, even though they
 were the same version as installed. This was somewhat counter-intuitive,
 so the new behaviour makes more sense. You should still need --deep
 though.

--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 libFOO.1 are dead or crashy or acting weired.

That happened to me several times. I see NO reason to use deep. Ever.

Reduced the occurences where I have to use revdep-rebuilt to almost nil 
(except that expat tragedy some weeks ago. Man that sucked ;) ).
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] Change profile

2006-06-01 Thread Anthony E. Caudel

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 working.

Tony

--
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety.
   -- Benjamin Franklin
--
gentoo-user@gentoo.org mailing list