View previous topic :: View next topic |
Author |
Message |
fusion Tux's lil' helper
Joined: 02 Nov 2002 Posts: 119
|
Posted: Fri Dec 20, 2002 6:37 pm Post subject: What is the -deep option for in emerge |
|
|
I know that you can do a emerge -u to update system or world but I read a post somewhere about doing a emerge -deep. I was wonding what the deep option does cause i cant find any documention on it. I have notice that if you do emerge -up the packages all have U's and if you do a emerge -p -deep there is a much longer list but they all have N's. At first I thought that the if you did emerge -u -deep if just updated more packages but again they all have N's not U's.
thanks |
|
Back to top |
|
|
Scandium Retired Dev
Joined: 22 Apr 2002 Posts: 340 Location: Germany
|
Posted: Fri Dec 20, 2002 6:53 pm Post subject: |
|
|
Hi,
the --deep method was introduced and you can do the following with it:
If you do emerge -u world it just updates the things listed in the world file and _not_ the dependancies (only if the updated package in the world file needs a newer package as a dependancy) and with --deep you tell emerge to update all packages and not just all packages listed in the world file...
(before --deep was introduced some people just added every installed package to the world file to -u world everything automatically...)
Another use is for emerge -e world...emerge -e world just recompiles all packages not compiled with your current set of gcc etc. but if combined with --deep everything is recompiled...
I am not 100% sure, though...Even if I am wrong (please someone correct me then) I think you can get a general idea of what the use of --deep can be usefull...
Last edited by Scandium on Fri Dec 20, 2002 11:23 pm; edited 1 time in total |
|
Back to top |
|
|
fusion Tux's lil' helper
Joined: 02 Nov 2002 Posts: 119
|
Posted: Fri Dec 20, 2002 7:05 pm Post subject: |
|
|
I understand now thanks a lot. |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Fri Dec 20, 2002 8:44 pm Post subject: |
|
|
First, don't get confused about the number of hyphens: there are two. --deep. -deep is the same as -d -e -e -p, which includes -e (emptytree) and will recompile everything.
Scandium wrote: | emerge -e world just recompiles all packages not compiled with your current set of gcc etc. but if combined with --deep everything is recompiled... | This is the first I've heard of this. Can anybody confirm? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
Scandium Retired Dev
Joined: 22 Apr 2002 Posts: 340 Location: Germany
|
Posted: Fri Dec 20, 2002 11:20 pm Post subject: |
|
|
I am not sure, though.
I just heard from a user in IRC when he does
emerge -e world
he gets informed on all packages which are already current that he should touch the ebuild to recompile, but with --deep it worked for him - that's the only explanation I have for this...I can't say it from my point of view though...so it's more a guess - but as I said...don't blame me on this one |
|
Back to top |
|
|
Lasker Guru
Joined: 17 Jul 2002 Posts: 445
|
Posted: Sat Dec 21, 2002 1:28 am Post subject: |
|
|
Scandium wrote: |
If you do emerge -u world it just updates the things listed in the world file and _not_ the dependancies (only if the updated package in the world file needs a newer package as a dependancy) and with --deep you tell emerge to update all packages and not just all packages listed in the world file...
|
But how does it fit to this?
I've got an update today of sylpheed by emerge -u --deep world, but not by a simple emerge -u world.
I can not imagine, that something depends on sylpheed (rather vice versa).
It was a single update, no other files/programs after the last emerge sync... |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Sat Dec 21, 2002 2:14 am Post subject: |
|
|
Only thing I could find that depends on sylpheed is sylpheed-iconset. Got that? _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
Lasker Guru
Joined: 17 Jul 2002 Posts: 445
|
Posted: Sat Dec 21, 2002 4:02 am Post subject: |
|
|
rac wrote: | Only thing I could find that depends on sylpheed is sylpheed-iconset. Got that? |
I have the iconset, but it's still the 'old' version which I installed, when I merged sylpheed-claws the first time.
It wasn't updated since then.
Once more: I've got only that update after the last sync!
This alone tells me that there hardly can be a dependency reason for the update... |
|
Back to top |
|
|
raluke n00b
Joined: 11 Aug 2002 Posts: 56 Location: Maryland, USA
|
Posted: Mon Dec 23, 2002 12:59 am Post subject: --pretend --emptytree question |
|
|
If I type "emerge --pretend --emptytree world", then the result is a listing of every package installed on my Gentoo Linux box? |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Mon Dec 23, 2002 1:01 am Post subject: Re: --pretend --emptytree question |
|
|
raluke wrote: | If I type "emerge --pretend --emptytree world", then the result is a listing of every package installed on my Gentoo Linux box? | Yes, with the exception of things you emerged with the oneshot option that are not dependencies of anything in the world file. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
raluke n00b
Joined: 11 Aug 2002 Posts: 56 Location: Maryland, USA
|
Posted: Mon Dec 23, 2002 1:21 am Post subject: --deep versus --deep --emptytree |
|
|
Okay, I'd like to extend the question, then.
I just found a thread on "--deep" from back in October in which somebody says that you can occasionally get in trouble doing "emerge --deep --update world" because a library might be recompiled and a third package might still want the library compiled in the old way.
I'm interpreting this to mean that the only way to get around that is to use "emerge --update --deep --emptytree world" ... which could take days on my PIII/500MHz box!
Am I understanding this correctly?
TIA,
-Robert |
|
Back to top |
|
|
rac Bodhisattva
Joined: 30 May 2002 Posts: 6553 Location: Japanifornia
|
Posted: Mon Dec 23, 2002 4:12 am Post subject: Re: --deep versus --deep --emptytree |
|
|
raluke wrote: | you can occasionally get in trouble doing "emerge --deep --update world" because a library might be recompiled and a third package might still want the library compiled in the old way. | That's possible, but I see no automated way around it.
Quote: | I'm interpreting this to mean that the only way to get around that is to use "emerge --update --deep --emptytree world" | Even that wouldn't do it, because the third package hasn't been updated yet. And --deep is superfluous in the face of --emptytree. _________________ For every higher wall, there is a taller ladder |
|
Back to top |
|
|
grafty n00b
Joined: 27 Jan 2003 Posts: 33
|
Posted: Mon Jan 27, 2003 8:13 am Post subject: |
|
|
(In case anyone is still curious about this old thread)
rac wrote: | First, don't get confused about the number of hyphens: there are two. --deep. -deep is the same as -d -e -e -p, which includes -e (emptytree) and will recompile everything.
Scandium wrote: | emerge -e world just recompiles all packages not compiled with your current set of gcc etc. but if combined with --deep everything is recompiled... | This is the first I've heard of this. Can anybody confirm? |
I can confirm the contrary:
Code: | etc # emerge -e world -p | wc -l
354
etc # emerge -e --deep world -p | wc -l
354
|
It looks to me as though emerge -e world operates the same with or without the --deep option. |
|
Back to top |
|
|
Lasker Guru
Joined: 17 Jul 2002 Posts: 445
|
Posted: Mon Jan 27, 2003 9:08 am Post subject: |
|
|
grafty wrote: |
I can confirm the contrary:
[code]etc # emerge -e world -p | wc -l
354
etc # emerge -e --deep world -p | wc -l
354
It looks to me as though emerge -e world operates the same with or without the --deep option. |
According to rac's comment it's no wonder:
rac wrote: |
...
And --deep is superfluous in the face of --emptytree.
|
And thus not contrary. |
|
Back to top |
|
|
grafty n00b
Joined: 27 Jan 2003 Posts: 33
|
Posted: Wed Jan 29, 2003 6:29 am Post subject: |
|
|
Lasker wrote: | grafty wrote: |
I can confirm the contrary:
[code]etc # emerge -e world -p | wc -l
354
etc # emerge -e --deep world -p | wc -l
354
It looks to me as though emerge -e world operates the same with or without the --deep option. |
According to rac's comment it's no wonder:
rac wrote: |
...
And --deep is superfluous in the face of --emptytree.
|
And thus not contrary. |
I was proving the contrary of Scandium's post...
Scandium wrote: | emerge -e world just recompiles all packages not compiled with your current set of gcc etc. but if combined with --deep everything is recompiled... |
And my quick examples did confirm the contrary of what Scandium posted. |
|
Back to top |
|
|
Scandium Retired Dev
Joined: 22 Apr 2002 Posts: 340 Location: Germany
|
Posted: Wed Jan 29, 2003 2:35 pm Post subject: |
|
|
grafty wrote: |
And my quick examples did confirm the contrary of what Scandium posted. |
yeah, and I said that I wasn't sure
sorry for that |
|
Back to top |
|
|
|