Summary: | "desired" stub | ||
---|---|---|---|
Product: | Portage Development | Reporter: | ivo welch <ivo.welch> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ivo welch
2004-12-02 05:50:37 UTC
This should be an external tool from portage; it's not portages business to do notifications of that sort (imo). hi brian: thanks. there are two arguments why emerge may be the right utility. first, the external tool needs to monitor the portage tree. emerge already does portage tree processing at rsync time. an alternative way would be a message that states at the end of the --sync run what packages have become newly available for our architecture. second, "emerge --update world" would be able to take advantage of the new package by itself. right now, I know that this rebuilds everything I need and want---except stuff that may have just become unblocked or available. regards, /iaw I'd agree with Brian... I'd suggest that "hooks" be used instead of direct integration. That's something else to wait for though. |