Summary: | Developers HOWTO needs updating. | ||
---|---|---|---|
Product: | [OLD] Docs-developer | Reporter: | Olivier Reisch (RETIRED) <doctomoe> |
Component: | Developers HOWTO | Assignee: | John Davis (zhen) (RETIRED) <zhen> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | doctomoe |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 8032 |
Description
Olivier Reisch (RETIRED)
2002-06-02 14:52:49 UTC
Do you have any ideas that you can post? I will try to add what I can, but I need some ideas from the ebuild developers! Thanks, //ZhEN OK, here are some suggestions: - Update of the ebuild variables listing, eg. remove A, add stuff like SLOT, LICENCE, etc. - Detail the workings of the ebuild keywording for multi platform compatibility and how to make use of the keywords to make plat form specific steps in an ebuild. (namely the x86, ppc, sparc and sparc64 keywords and how to use them, etc.) - Make sure all the USE variables are up to date in the listing - Make a clear reference to the CVS guide, which I think needs updating too. It should specifically show how a new developer switches from an rsync mirror to the CVS mirror (for emerge rsync for instance), how to check out the current CVS portage tree, how to enable keychains, what lintool and repoman are and how to use them. Some of this is referenced in http://gentoo.org/~karltk/POLICY.txt and I believe adding most of this document into the Developer HowTO would be a good idea. If that'd all be done, we would already have a way better Developer HowTO :) Thanks for your work. I will take care of this when I get a chance. It needs done! //ZhEN Is there a way to rsync to the cvs tree? //ZhEN I covered all of this, look to the webpage, cause it will be there on the next update ;-) //ZhEN |