Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 86209 - Control of Emerge that require manual intervention
Summary: Control of Emerge that require manual intervention
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
: 140682 (view as bug list)
Depends on:
Reported: 2005-03-21 20:16 UTC by Mike Slinn
Modified: 2006-07-16 12:16 UTC (History)
1 user (show)

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


Note You need to log in before you can comment on or make changes to this bug.
Description Mike Slinn 2005-03-21 20:16:27 UTC
How about a new emerge flag that prevents installations which require manual install, or a flag that interrupts a series of emerges (such as result from emerge -uD world) before installing a package that requires manual action?  The user would be warned that the next package will require manual intervention, then they would OK the installation of that package, and the emerge would stop after that package gets installed. I realize that extra information might need to be added to package definitions in order for this to work.  The recent change to httpd's file layout b0rked our servers and we could have controlled the process better with this capability.

Reproducible: Always
Steps to Reproduce:
Comment 1 Jason Stubbs (RETIRED) gentoo-dev 2005-03-22 06:25:18 UTC
There is no line - at least that I can see - to define whether an update will require modification to system settings or not. In your case, an upgrade of apache from version X to version Y caused you problems and a similar upgrade from version X to version Z would to, but if Y to Z doesn't cause problems then how should Z be marked? If you can see a way to do it cleanly, feel free to bring it up for discussion on the mailing list. However, it's never a good idea to upgrade servers that are in use anyway.
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-07-16 12:16:50 UTC
*** Bug 140682 has been marked as a duplicate of this bug. ***