public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Tiziano Müller" <dev-zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC:sys-apps/portage @overlay atoms postfix support
Date: Sun, 24 May 2009 21:28:25 +0200	[thread overview]
Message-ID: <1243193305.8346.189.camel@localhost> (raw)
In-Reply-To: <fv426vlke7k7cug6g5UYAxe124vaj_firegpg@mail.gmail.com>

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

Am Sonntag, den 24.05.2009, 20:04 +0200 schrieb lxnay@sabayonlinux.org:
> 
> On Sun, May 24, 2009 at 7:03 PM, Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> > On Sun, 24 May 2009 19:04:08 +0200 (CEST)
> > lxnay@sabayonlinux.org wrote:
> >> app-admin/equo (sabayon overlay -- Entropy Framework client) supports
> >> the postfix "@repository" to let users force the installation of a
> >> package from a specific repository.
> >
> > @ is used by Portage for sets. Paludis has been using ::repo for repo
> > dependencies for years. Why not go with the established syntax?
> 
> I wrote "postfix" not "prefix". Sets use "@" prefix.
> Regarding your "why", why not going through GLEP and gentoo-dev acceptance ;) ?
> 
> >
> >> Users of multiple repositories seem to appreciate the freedom that is
> >> brought with this small-but-effective(TM) feature.
> >
> > Note that Portage doesn't support multiple repositories, so this one's
> > probably not very straight-forward... It supports overlays, which means
> > only one thing is ultimately visible for a c/p-v.
> 
> I know.
> 
> >
> > --
> > Ciaran McCreesh
> >
> 
> I am wondering if enabling @overlay postfix support could be just restricted to command line arguments, at least for the beginning.

And then it's a pm thing. So the person you want to talk about it is
zmedico.

-- 
Tiziano Müller
Gentoo Linux Developer, Council Member
Areas of responsibility:
  Samba, PostgreSQL, CPP, Python, sysadmin, GLEP Editor
E-Mail   : dev-zero@gentoo.org
GnuPG FP : F327 283A E769 2E36 18D5  4DE2 1B05 6A63 AE9C 1E30

[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-05-24 19:28 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 17:04 [gentoo-dev] RFC:sys-apps/portage @overlay atoms postfix support lxnay
2009-05-24 17:03 ` Ciaran McCreesh
2009-05-24 18:04   ` lxnay
2009-05-24 19:28     ` Tiziano Müller [this message]
2009-05-25  6:30       ` lxnay
2009-05-25 13:43     ` Alex Legler
2009-05-25 15:28       ` lxnay
2009-05-25 15:38         ` AllenJB
2009-05-25 15:52           ` Dale
2009-06-02  8:18           ` [gentoo-dev] " Steven J Long
2009-06-02 13:04             ` Duncan
2009-06-03 23:51               ` Piotr Jaroszyński
2009-06-04  7:09                 ` Duncan
2009-05-25 18:37         ` [gentoo-dev] " Robert Buchholz
2009-05-25 20:24           ` Ben de Groot
2009-05-25 20:32             ` Robert Buchholz
2009-05-26  8:13               ` lxnay
2009-05-26 13:20                 ` Ciaran McCreesh
2009-05-26 17:20                   ` Nirbheek Chauhan
2009-05-26 19:31                 ` Petteri Räty
2009-05-24 17:20 ` Nirbheek Chauhan
2009-05-24 17:28   ` Ciaran McCreesh
2009-05-24 17:35     ` Nirbheek Chauhan
2009-05-24 17:56       ` Ben de Groot
2009-05-25 19:21 ` Josh Saddler

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=1243193305.8346.189.camel@localhost \
    --to=dev-zero@gentoo.org \
    --cc=gentoo-dev@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