On Sun, 2005-08-21 at 11:14 -0400, Nathan L. Adams wrote: > Its a chicken and egg situation. I need to have a certain level of > expertise with ebuild syntax and conventions to do the job. So I've > asked for some help from an expert. Also, I learn things quicker and > easier by first seeing examples and then seeing the documentation; > that's just me. Once I've learned a bit, I can start doing things on my > own.
We have plenty of examples in portage - and you can always ask on irc or on this mailing list if you have a specific question related to ebuild best practices. Did you read our Ebuild HOWTO [1] yet? > By the way, I didn't create the ebuild. Peer review isn't when you > review your own work. Its when somebody else, knowlegdable in the > subject, reviews your work. Yes, I am aware of the concept. > *THAT* is a great idea. I am proficient in several scripting languages. > I am willing to write the tools if someone more knowledgable is willing > to help me with what the 'best practices' are for ebuilds. Its a 'you > help me and we'll both help Gentoo' situation. Good luck with that. I look forward to hearing from you when you've established a project base and started reviewing our current ebuilds. Wikipedia has an article on code review [2] which has a few useful links at the bottom - perhaps these can help you get started. Sincerely, Brix [1]: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 [2]: http://en.wikipedia.org/wiki/Code_review -- Henrik Brix Andersen <[EMAIL PROTECTED]> Gentoo Metadistribution | Mobile computing herd
signature.asc
Description: This is a digitally signed message part
