Summary: | --keep-going should (not) be made a default | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Casey Jones <jonescaseyb> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | jer |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Casey Jones
2009-01-31 19:43:46 UTC
Hmm, ever tried the --keep-going option? " Continue as much as possible after an error. When an error occurs, dependencies are recalculated for remaining packages and any with unsatisfied dependencies are automatically dropped. Also see the related --skipfirst option." Perhaps it should be enabled by default? Is there any reason why it shouldn't? Use EMERGE_DEFAULT_OPTS in make.conf, a global default would probably counterintuitive and counterproductive. I don't see how it's counterintuitive or counterproductive. Is there any risk to enabling it? (In reply to comment #4) > I don't see how it's counterintuitive or counterproductive. > > Is there any risk to enabling it? Yes, because in the end people see the process has finished and may not heed the warnings that some packages actually failed to build, particularly when dozens of packages are emerged in the same go. The current default behaviour is to make the admin stop and fix the problem instead of trying to paste over it while breakage builds upon breakage because everything seems alright. We have to be very careful about changing default behavior because it affects everyone and even the slightest change can potentially upset lots of users. I agree with comment #5. If you want it enabled by default then use EMERGE_DEFAULT_OPTS. |