Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 319871 - emerge --accept <version> switch
Summary: emerge --accept <version> switch
Status: RESOLVED DUPLICATE of bug 280097
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-15 18:49 UTC by dE
Modified: 2010-05-15 20:31 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dE 2010-05-15 18:49:05 UTC
Opening the package.keyword or package.unmask each time for adding packages is tiresome.

So I propose an --accept switch which will automatically add the latest packages to package.keyword and start emerging. If there are masked dependencies which will have to be compiled to satisfy the package's dependencies, all will be added to package.keyword so as to pull the latest version but after showing a the list of keyworded packages and asking if to merge them or not (similar to --ask). Since most people prefer to make portage work at night, you might add a --assume-yes switch to portage also (it is there in apt) to make the process non-interactive.

It's a bad idea to add entries to package.mask simply to satisfy dependencies since these packages are really unstable, and we usually don't encounter such packages from the original portage tree.

--accept might have another option to accept a specific version in the following formats - 

emerge --accept <package version; not the complete package name> <package>; other packages (masked dependencies) will compile with the latest version.

You might add another option to emerge the lowest masked version instead - 

emerge --accept lowest <package>

Reproducible: Always

Steps to Reproduce:
Comment 1 Zac Medico gentoo-dev 2010-05-15 20:31:01 UTC

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