From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23629 invoked from network); 25 Nov 2004 09:45:10 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 25 Nov 2004 09:45:10 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.41) id 1CXGBa-0003ga-EM for arch-gentoo-dev@lists.gentoo.org; Thu, 25 Nov 2004 09:45:10 +0000 Received: (qmail 28184 invoked by uid 89); 25 Nov 2004 09:44:49 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 5881 invoked from network); 25 Nov 2004 09:44:48 +0000 Date: Thu, 25 Nov 2004 18:44:45 +0900 From: Georgi Georgiev To: gentoo-dev@lists.gentoo.org Message-ID: <20041125094444.GA13530@lion.gg3.net> Mail-Followup-To: gentoo-dev@lists.gentoo.org References: <200411222345.14487.vapier@gentoo.org> <3908185A3D2C144E9FAD070D2727FFD81716A9@PERIMAIL.perimed.priv> <921ad39e04112306381595bc8a@mail.gmail.com> <1049C878-3D68-11D9-9250-000A958238BC@gentoo.org> <1101226835.9000.39.camel@cgianelloni.nuvox.net> <46059ce104112315265d557064@mail.gmail.com> <1101327015.9848.5.camel@io> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1101327015.9848.5.camel@io> User-Agent: Mutt/1.5.6i Subject: Re: [gentoo-dev] Gentoo beeping at me! X-Archives-Salt: 3fec71e2-3ac9-47bd-af8b-ef80276c9cbf X-Archives-Hash: 420f807eb1ba022f9f9c92d48c419657 maillog: 24/11/2004-21:10:14(+0100): Benjamin Schindler types > I've got to throw an idea in here.... How about a doxygen-style > documentation? No, it doesn't have to be doxygen, but I'm thinking of > this idea. Instead of looking at every eclass, why not have some > standard-format documentation in an eclass itself and let a tool create > the documentation in whichever format he wishes to do so. > Just my 2 cents... Yep, was about to propose something based on perl's POD, but realized it might be a little ugly to keep a large section of comment-ed out to-be documentation in the eclass itself. Or are you having something different in mind? -- *> Georgi Georgiev *> You will be traveling and coming into a *> <* chutz@gg3.net <* fortune. <* *> +81(90)6266-1163 *> *> -- gentoo-dev@gentoo.org mailing list