Bug 66974

Summary:	Please do not hardcode warning delays, make them configurable
Product:	Portage Development	Reporter:	Holger Hoffstätte <holger>
Component:	Enhancement/Feature Requests	Assignee:	Portage team <dev-portage>
Status:	RESOLVED FIXED
Severity:	enhancement	CC:	radek
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Holger Hoffstätte 2004-10-10 06:27:10 UTC

portage 2.0.51 introduced several warnings e.g. about emerge-ing /path/to/ebuild etc. While from a general POV it might be desirable to prevent people from messing up their system, I'd like to be able to configure these timeouts and - if possible - turn them off. I find these warnings highly annoying when writing my own ebuilds. Besides, hardcoded values are not good practice. ;)


Reproducible: Always
Steps to Reproduce:
1. emerge /path/to/some/ebuild
2. waste..10..seconds..of..my..life
3. grumble




Suggestion: PORTAGE_WARN_DELAY >0 shows the warnings, 0 suppresses them and lets
me break my system without too much pampering.

Comment 1 Holger Hoffstätte 2005-01-13 11:44:50 UTC

Closing this since the delay can be configured in portage now..although it's a little bit underdocumented. :)