public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris PeBenito <pebenito@gentoo.org>
To: dnellans@cs.utah.edu
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] ebuild naming policy
Date: 15 Apr 2003 18:20:36 -0500	[thread overview]
Message-ID: <1050448836.3487.17.camel@chris.pebenito.net> (raw)
In-Reply-To: <1050450162.18807.6.camel@malfus>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

You can see the naming policy in the Gentoo Development policy:
http://www.gentoo.org/doc/en/policy.xml

Chris

On Tue, 2003-04-15 at 18:42, Dave Nellans wrote: 
> do we have an established naming policy for ebuilds, and where can i
> find it?
-- 
Chris PeBenito
<pebenito@gentoo.org>
Developer, Gentoo Linux
Hardened Gentoo Project
 
"Engineering does not require science. Science helps
a lot, but people built perfectly good brick walls
long before they knew why cement works."-Alan Cox

Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xE6AF9243
Key fingerprint = B0E6 877A 883F A57A 8E6A  CB00 BC8E E42D E6AF 9243


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2003-04-15 23:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-15 23:42 [gentoo-dev] ebuild naming policy Dave Nellans
2003-04-15 23:16 ` Jon Portnoy
2003-04-16  0:03   ` Dave Nellans
2003-04-15 23:43     ` Fred Van Andel
2003-04-16  0:11     ` George Shapovalov
2003-04-16  0:58       ` Dave Nellans
2003-04-16  0:35         ` Peter Ruskin
2003-04-16  1:39           ` Jeff Rose
2003-04-16  2:43             ` George Shapovalov
2003-04-16  8:15               ` Paul de Vrieze
2003-04-16 13:30                 ` Chris Bainbridge
2003-04-15 23:20 ` Chris PeBenito [this message]

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=1050448836.3487.17.camel@chris.pebenito.net \
    --to=pebenito@gentoo.org \
    --cc=dnellans@cs.utah.edu \
    --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