public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: Brian Harring <ferringb@gmail.com>
Cc: gentoo-soc@lists.gentoo.org, zmedico@gentoo.org
Subject: Re: [gentoo-soc] Multiple Repository Support in Portage - Week 3
Date: Sat, 19 Jun 2010 22:37:30 +0100	[thread overview]
Message-ID: <20100619223730.70f732b0@snowcone> (raw)
In-Reply-To: <20100619201821.GK12490@hrair>

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

On Sat, 19 Jun 2010 13:18:21 -0700
Brian Harring <ferringb@gmail.com> wrote:
> From pkgcore's view, the 1st ':' is required- if there is no slot
> dep, leave it empty.  The second demarks the start of a repository
> dep.

I prefer the "always ::" form, simply because it's easier to go "if
repo, then add ::repo" than it is to go "if repo, then add :repo, but
also stick another : in there if we've not done a slot". What a repo
dep looks like shouldn't change based upon whether there's also a slot
dep there.

> > Also note that that specifically only covers packages that are *in*
> > the ::gentoo repository. The package you have installed *from* the
> > gentoo repository is ::gentoo->/ or ::gentoo->installed .
> 
> '->' doesn't work very well though; specifically, the '-' is allowed 
> as part of a repository name.  Backtracking parsers can handle that 
> fine, it's just nonoptimal to have one of the splitter char's be part 
> of the allowed character set for a name.

Eh, I'd hardly take "your parser must support a single character
lookahead" to be a defining argument, especially when you consider the
mess that's needed to split pkg-ver up.

> @, or some other char that is explicitly disallow seems a better 
> choice.

The rationale behind -> is that it reads clearly. ::from->to reads like
what it does. Experience has shown that users do need and make use of
both forms (although unfortunately they're less inclined to appreciate
the difference between ::installed and ::/ ), so it's best to pick
something they can eventually understand.

On a semi-related note: real world experience has also shown that every
time we've thought about using ::repo deps of any kind in a repository
rather than a user context, it's been the wrong thing to do, and the
right thing to do is almost always [feature(-)].

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-06-19 21:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-15 15:57 [gentoo-soc] Multiple Repository Support in Portage - Week 3 Otávio Pontes
2010-06-15 17:42 ` Auke Booij
2010-06-15 22:11   ` Brian Dolbec
2010-06-15 22:56     ` Otávio Pontes
2010-06-16 14:36       ` Otávio Pontes
2010-06-16 15:47         ` Auke Booij
2010-06-16 16:36           ` Nirbheek Chauhan
2010-06-19  3:48           ` Brian Harring
     [not found]             ` <20100619120615.24f9c07e@snowcone>
2010-06-19 20:18               ` Brian Harring
2010-06-19 21:37                 ` Ciaran McCreesh [this message]
2010-06-19 22:43                   ` Brian Harring
2010-06-22 13:01                 ` Otávio Pontes
2010-06-16 16:58         ` Zac Medico

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=20100619223730.70f732b0@snowcone \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=ferringb@gmail.com \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=zmedico@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