Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 58039 - emerge world should imply --oneshot
Summary: emerge world should imply --oneshot
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-23 02:50 UTC by Matteo Settenvini
Modified: 2004-07-23 08:45 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
Proposed patch (emerge.patch,578 bytes, patch)
2004-07-23 02:51 UTC, Matteo Settenvini
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Matteo Settenvini 2004-07-23 02:50:16 UTC
It would be useful if "emerge world" would imply --oneshot. This would mean that dependencies to manually merged packages aren't inserted in /var/cache/edb/world when updating the system, keeping the world file clean.

This is interesting, because if a package doesn't need a particular dep any more and it is filed in the world file, it will remain as a pkg to merge even if not requested.

It could also be an acceptable workaround for bug #41407 (although not doing what stated there).

Reproducible: Always
Steps to Reproduce:
Comment 1 Matteo Settenvini 2004-07-23 02:51:23 UTC
Created attachment 35995 [details, diff]
Proposed patch

Sorry for the low quality of the patch, but I am a newbie...
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2004-07-23 02:59:32 UTC
emerge world should not be adding anything to the world file, regardless of whether --oneshot is used. Can you give an example of when/how this happens? If possible, exact steps to reproduce would be nice. Also, what portage version are you using?
Comment 3 Matteo Settenvini 2004-07-23 08:45:08 UTC
whoops. you're right. this bug was present on an old copy of portage (I've an old machine I never update, that was running portage as for 3Q-2003). This bug has gone when updatig the portage on that machine (in fact, another pc I have that I keep in daily sync with pkg updates doesn't show the problem).

Marking invalid, and sorry for the issue. I just believed it was still appliable.