public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Brian Harring <ferringb@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
Subject: Re: [gentoo-soc] Multiple Repository Support in Portage - Week 3
Date: Fri, 18 Jun 2010 20:48:54 -0700	[thread overview]
Message-ID: <20100619034854.GH12490@hrair> (raw)
In-Reply-To: <AANLkTim4T9-keir7ae-64kIQl-sCbERhj5fcc8u-Hs7a@mail.gmail.com>

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

On Wed, Jun 16, 2010 at 05:47:42PM +0200, Auke Booij wrote:
> 2010/6/16 Otávio Pontes <otaviobp@gmail.com>:
> > I couldn't find in paludis documentation (nor in pkgcore) where should
> > go repository name when using useflags to emerge a package.
> 
> I don't think it's considered "right" to depend on a /repository/.
> Instead, you depend on packages, versions, slots and useflags, but if
> you really want to be able to do this I guess you should speak with
> the PM devs.

It's actually alright- both from the commandline, and ebuild's 
specifying explicit repository deps.  Ebuild's rarely should be 
doing this in my opinion, but there are instants where it's 
necessary in my experience.  Basically, leave the support there, if 
people really care they get to add some marker to the repository 
blocking usage of repo deps.

As for syntax, it's cat/pkg:slotting-if-any:repo[flag-bits]

So for specifying a slot and a repo, and disabling build, 
sys-apps/portage:0:gentoo[-build]

If you don't care about the slot, you leave it empty- 
sys-apps/portage::gentoo[-build]

CC'ing ciaran either way- in testing paludis 0.46, 
sys-apps/portage:0:gentoo isn't flying... (the use ordering however 
does).

~harring

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

  parent reply	other threads:[~2010-06-19  3:51 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 [this message]
     [not found]             ` <20100619120615.24f9c07e@snowcone>
2010-06-19 20:18               ` Brian Harring
2010-06-19 21:37                 ` Ciaran McCreesh
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=20100619034854.GH12490@hrair \
    --to=ferringb@gmail.com \
    --cc=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-soc@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