| Summary: | Handbook lacks instructions for moving a package between categories | ||
|---|---|---|---|
| Product: | Community Relations | Reporter: | Stuart Herbert (RETIRED) <stuart> |
| Component: | Developer Relations | Assignee: | Gentoo Community Relations Team <comrel> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://dev.gentoo.org/~plasmaroo/gentoo-docs/hb-guide-ebuild-maintaining.html | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Stuart Herbert (RETIRED)
2004-07-22 02:20:57 UTC
Yes. a) An 'ebuild policy' document perhaps isn't the most obvious place to look for this information, given that this is a handbook and not simply a collection of individual documents. b) There's no mention of epkgmove. Does adding a single line to 'profiles/updates' actually move the package in CVS? Best regards, Stu no. adding the line to the updates file is how you tell portage what you moved around in cvs. epkgmove is a bit touchy at times, but it's pretty useful when it does work... I'm not sure we should put it in the handbook because AFAIK (and I might be wrong) it's not production ready... http://dev.gentoo.org/~plasmaroo/gentoo-docs/hb-guide-ebuild-maintaining.html should now cover this - I've added in both "Doing It The CVS Way <TM>" and "epkgmove". Please tell me if things need more detail or any changes you would like. Draft merged into the Handbook - closing as FIXED. |