Summary: | sys-apps/portage (and echangelog): Automated ChangeLog generation has different behavior for Manifest file | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Samuli Suominen (RETIRED) <ssuominen> |
Component: | Current packages | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | polynomial-c, tools-portage |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Samuli Suominen (RETIRED)
2011-10-30 17:03:36 UTC
=app-portage/gentoolkit-dev-0.2.8 =sys-apps/portage-9999 (checkout from yesterday) (In reply to comment #0) > This doesn't look normal. The behavior should match. I'm not sure in which > one the bug is, Portage or echangelog. > > ssuominen@null ~/gentoo-x86/x11-terms/sakura $ echangelog "Regenerate Manifest > wrt #388993 by Samuel BAUER" > ** > ** NOTE: No non-trivial changed files found. Normally echangelog > ** should be run after all affected files have been added and/or > ** modified. Did you forget to cvs add? > ** > ** In strict mode, exiting > ** If you know what you're doing there pass '--no-strict' to echangelog I think the echangelog --no-strict option will make it behave more like repoman. I don't care which one will be made the default, but one should be picked, and the default behavior needs to be consistent in both. IMO the only real solution to this is to teach repoman how to deal with eclass and profiles dirs. This is desirable for other reasons as well. (In reply to comment #4) > IMO the only real solution to this is to teach repoman how to deal with > eclass and profiles dirs. This is desirable for other reasons as well. How is that related to this bug? (In reply to comment #2) > I think the echangelog --no-strict option will make it behave more like > repoman. So how about making --no-strict default then? The behaviours are still different after nearly a year. Can we at least decide which one should be changed? The tree is literally getting polluted by pointless Manifest -only ChangeLoge entries. (In reply to comment #5) > The tree is literally getting polluted by pointless Manifest -only > ChangeLoge entries. Doesn't the change from bug 398009 help? Since that change, it will only generate a Manifest-only ChangeLog entry if you use --echangelog=force. (In reply to comment #5) > (In reply to comment #4) > > IMO the only real solution to this is to teach repoman how to deal with > > eclass and profiles dirs. This is desirable for other reasons as well. > > How is that related to this bug? Then echangelog can go, which solves your "the tools differ in behaviour" problem. |