Bug 53387

Summary:	--ignore-blockers for changing virtuals
Product:	Portage Development	Reporter:	Christian Birchinger (RETIRED) <joker>
Component:	Core - Interface (emerge)	Assignee:	Portage team <dev-portage>
Status:	RESOLVED DUPLICATE
Severity:	enhancement	CC:	radek
Priority:	High	Keywords:	Inclusion
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Christian Birchinger (RETIRED) gentoo-dev

2004-06-09 03:52:54 UTC

The ability of upgrading one packagename with another would shrink the timeframe where a system cannot be used. For example if you have XFree
installed and update to Xorg, you have to unmerge XFree first because it
blocks. Depending on the power of the machine, this can mean 2-3h without X.

All those problems could be avoided if emerge would let you upgrade from XFree
directly to Xorg. The same way as you usualy upgrade an app from version 1.0
to 1.1.


Reproducible: Always
Steps to Reproduce:
n/a
Actual Results:  
n/a

Expected Results:  
n/a

The big question is which kind of syntax could be used for this.
If the portage-devs have no perfect solution for the syntax, maybe the
a request for suggestions should be sent to the dev-mailinglist.

Something like slackware uses would be:
emerge -u x11-base/xfree%x11-base/xorg
(a % as seperator)

Having something in the ebuild which describes the "next hop" isn't really
usable because except for updates like XFree->Xorg the "new appname" cannot
be guessed (Like when updating from Sendmail to Exim for example).

Comment 1 Jason Stubbs (RETIRED) gentoo-dev

2005-05-02 04:48:40 UTC


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