Summary: | portage package does not have a ChangeLog in Portage! | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Andrew Cowie <andrew> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Andrew Cowie
2004-04-14 18:18:21 UTC
If I used that changelog, no one would read it anyway. Seriously. Do you care if I moved a conditional to prevent a traceback that you were unaware of and/or unaffected by? There is way too much internal changing to list the application changelog in that ChangeLog. If you want to know, you can put up the effort. Also, if it's that critical, then you should probably check the internals changelog, as well as read the documentation for change details too. A "What's New" File might start appearing in the next series. Well, to use your example, if all you changed was a conditional, then just say so. "Minor bug fixes". On the other hand, if it was a major change, then please indicate that... It's actually the broad brush differences that users/admins need to know about IMHO. As I said, emerge -lp is a really powerful feature, and I encourage you leverage it. Later, AfC |