Summary: | feature request: pre-emerge messages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Marcel J. P. Möhring <mjp.m> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Marcel J. P. Möhring
2003-12-01 16:46:39 UTC
with case #1 you'd have to emerge majority of those deps anyways with case #2 you have Bug 11359 *** This bug has been marked as a duplicate of 11359 *** no, there is no concept of 'message before an emerge with depends' there is concept of 'message before a specific emerge' that is, you can display a message before a merge only if for that one merge (in this case a message before the galeon emerge but not before its DEPEND) imho i dont think it's needed considering the # of cases where it'd be used last one: I agree, need would be limited for pre-emerge-pre-depend messages. The only problem I see with pre-emerge-only messages is, that you still gonna miss the really important messages, because when using X and emerging in console, you don't know, when the emerge of the 'wanted' packet begins, so you don't know, when to look at emerge process to eventually break it. But with the (new) logging ability in Bug 11359 as a workaround it should be possible to send emerge log to root window on X and therefore to actually be fast enough to break emerge for the wanted packet before you have to re-emerge it to get some options enabled. Make sense for me. :-D |