45493 – emerge -p command line dependency resolution

Bug 45493 - emerge -p command line dependency resolution

Summary: emerge -p command line dependency resolution

Status:	RESOLVED DUPLICATE of bug 1343

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Interface (emerge) (show other bugs)
Hardware:	All All

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2004-03-23 05:49 UTC by Jon Scott
Modified:	2005-07-17 13:06 UTC (History)
CC List:	0 users

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jon Scott 2004-03-23 05:49:11 UTC

It would be extremely useful if emerge -p (and -ep) took account of all the ebuilds specified on the command line when building its dependency tree.

For example, currently "emerge -p gentoo-sources nvidia-kernel" will pull in, amongst other things, everything required for gentoo-sources, then a default kernel (generally different, depending on the virtuals file), then nvidia-kernel itself.

A second example: on a system with no apache or mod_php installed, "emerge -p =apache-1.3.29-r1 mod_php" will pull in everything for apache1, then apache2, then mod_php itself. Obviously this doesn't happen if apache1 is installed before doing "emerge -p mod_php".

Comment 1 SpanKY gentoo-dev

2004-03-24 20:22:23 UTC


*** This bug has been marked as a duplicate of 1343 ***