From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuild Readability Issues
Date: Mon, 2 Dec 2002 11:03:08 -0500 [thread overview]
Message-ID: <200212021103.08386.vapier@gentoo.org> (raw)
In-Reply-To: <20021202130418.7077eac1.rcm@sasaska.net>
On Monday 02 December 2002 07:04, Rafael Cordones Marcos wrote:
> Yes, but, lets face it, documentation allways lags behind code. That's
> why if I see an ebuild that conains a reference to ${PACKAGE NAME} I do
> not have to goo look for any documentation to understand what it means
> (as compared to ${P}).
read `man 5 ebuild` ... its *very* up to date ... i update it on every release
of portage :P ... this goes for all manpages that portage installs ...
as for using ${PACKAGE NAME} in an ebuild, thats just what someone chose to
use as a variable, it has no 'official' value ...
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2002-12-02 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 11:23 [gentoo-dev] Ebuild Readability Issues Rafael Cordones Marcos
2002-12-02 12:06 ` Johannes Ballé
2002-12-02 12:04 ` Rafael Cordones Marcos
2002-12-02 13:03 ` foser
2002-12-03 16:54 ` Johannes Ballé
2002-12-02 16:03 ` Mike Frysinger [this message]
2002-12-03 13:15 ` Rafael Cordones Marcos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200212021103.08386.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox