| 1 |
On Sat, Jun 19, 2010 at 17:18, Brian Harring <ferringb@×××××.com> wrote: |
| 2 |
> On Sat, Jun 19, 2010 at 12:06:15PM +0100, Ciaran McCreesh wrote: |
| 3 |
>> I'm not subscribed to the SOC list, so if this doesn't make it through, |
| 4 |
>> please repost... |
| 5 |
>> |
| 6 |
>> On Fri, 18 Jun 2010 20:48:54 -0700 |
| 7 |
>> Brian Harring <ferringb@×××××.com> wrote: |
| 8 |
>> > On Wed, Jun 16, 2010 at 05:47:42PM +0200, Auke Booij wrote: |
| 9 |
>> > > 2010/6/16 Otávio Pontes <otaviobp@×××××.com>: |
| 10 |
>> > > > I couldn't find in paludis documentation (nor in pkgcore) where |
| 11 |
>> > > > should go repository name when using useflags to emerge a package. |
| 12 |
>> |
| 13 |
>> http://paludis.pioto.org/configuration/specs.html is what Paludis |
| 14 |
>> supports for user specs. |
| 15 |
>> |
| 16 |
>> > As for syntax, it's cat/pkg:slotting-if-any:repo[flag-bits] |
| 17 |
>> > |
| 18 |
>> > So for specifying a slot and a repo, and disabling build, |
| 19 |
>> > sys-apps/portage:0:gentoo[-build] |
| 20 |
>> > |
| 21 |
>> > If you don't care about the slot, you leave it empty- |
| 22 |
>> > sys-apps/portage::gentoo[-build] |
| 23 |
>> > |
| 24 |
>> > CC'ing ciaran either way- in testing paludis 0.46, |
| 25 |
>> > sys-apps/portage:0:gentoo isn't flying... (the use ordering however |
| 26 |
>> > does). |
| 27 |
>> |
| 28 |
>> ::gentoo not :gentoo (and only in contexts where it's a 'user' dep |
| 29 |
>> spec, not one covered by an EAPI). |
| 30 |
> |
| 31 |
> |
| 32 |
> Crapola. Didn't notice that paludis requires doubling up there- |
| 33 |
> specifically, for pkgcore |
| 34 |
> |
| 35 |
> sys-apps/portage |
| 36 |
> sys-apps/portage:0 |
| 37 |
> sys-apps/portage:0:gentoo |
| 38 |
> sys-apps/portage::gentoo |
| 39 |
> sys-apps/portage:0:gentoo[-build] |
| 40 |
> sys-apps/portage::gentoo[-build] |
| 41 |
> |
| 42 |
> From pkgcore's view, the 1st ':' is required- if there is no slot dep, |
| 43 |
> leave it empty. The second demarks the start of a repository dep. |
| 44 |
> |
| 45 |
> For paludis, it's based on consecutive ':' ; so literally the above is |
| 46 |
> sys-apps/portage |
| 47 |
> sys-apps/portage:0 |
| 48 |
> sys-apps/portage:0::gentoo |
| 49 |
> sys-apps/portage::gentoo |
| 50 |
> sys-apps/portage:0::gentoo[-build] |
| 51 |
> sys-apps/portage::gentoo[-build] |
| 52 |
|
| 53 |
I am doing exactly this way now. With '::', after slot and before useflags. |
| 54 |
|
| 55 |
> |
| 56 |
> |
| 57 |
> People's feedback is kind of needed on that one due to the diff. in |
| 58 |
> syntax... |
| 59 |
> |
| 60 |
> |
| 61 |
>> Also note that that specifically only covers packages that are *in* |
| 62 |
>> the ::gentoo repository. The package you have installed *from* the |
| 63 |
>> gentoo repository is ::gentoo->/ or ::gentoo->installed . |
| 64 |
> |
| 65 |
> '->' doesn't work very well though; specifically, the '-' is allowed |
| 66 |
> as part of a repository name. Backtracking parsers can handle that |
| 67 |
> fine, it's just nonoptimal to have one of the splitter char's be part |
| 68 |
> of the allowed character set for a name. |
| 69 |
> |
| 70 |
> @, or some other char that is explicitly disallow seems a better |
| 71 |
> choice. |
| 72 |
> |
| 73 |
> Comments? |
| 74 |
> |
| 75 |
> thanks- |
| 76 |
> ~harring |
| 77 |
> |
Archives