public inbox for gentoo-pms@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] Re: [PATCH] Allocate __* for package manager internals, blacklist it for ebuilds.
Date: Sun, 16 Sep 2012 18:14:03 +0200	[thread overview]
Message-ID: <20565.64203.480058.568298@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20120916072418.GJ28593@localhost>

>>>>> On Sun, 16 Sep 2012, Brian Harring wrote:

> I'd frankly rather it in both locations.  Ebuild devs are more likely 
> to read the sections I tagged w/ this info, imo.

I doubt that many ebuild devs will consult the PMS to find out about
reserved names.

The only way to ensure that __* names are not used in ebuilds is to
enforce it with repoman. And maybe add a note in the devmanual.

Ulrich


  parent reply	other threads:[~2012-09-16 16:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1347327593%2d1144-1-git-send-email-ferringb@gmail.com>
2012-09-16  6:45 ` [gentoo-pms] Re: [PATCH] Allocate __* for package manager internals, blacklist it for ebuilds Ulrich Mueller
2012-09-16  7:24   ` Brian Harring
2012-09-16 15:06     ` Ciaran McCreesh
2012-09-16 16:14     ` Ulrich Mueller [this message]
2012-09-18 23:59       ` Brian Harring
2012-09-19  5:22         ` Ulrich Mueller

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=20565.64203.480058.568298@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-pms@lists.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