Re: [gentoo-soc] Multiple Repository Support in Portage - Week 3

["Otávio Pontes" <otaviobp@gmail.com>]

On Tue, Jun 15, 2010 at 19:11, Brian Dolbec <brian.dolbec@gmail.com> wrote:
> On Tue, 2010-06-15 at 19:42 +0200, Auke Booij wrote:
>> Paludis actually puts the repository name after the package, for
>> example app-portage/eix::gentoo. Is there any specific reason you
>> decided to do it your way? I don't know how pkgcore does this, btw,
>> just interested to hear your reasoning.

There isn't a specific reason i did this way. Actually, i have read
the Paludis docs and copied the '::' from they. But i misunderstood.
I will change it to fit the paludis and pkgcore way.
Thanks for the hint.

Otávio Pontes

>>
>> tulcod.
>
>
> Yes pkgcore is the same repo syntax as paludis.  So why mess with a
> standard the other 2 package mangers have had for a few years already?
> It'll be confusing as hell for users trying to figure out and keep
> straight between PM's and forum postings saying one way, then another.
> Also for someone like me coding a gui frontend it means having 2
> different code blocks to do the same thing, one for each syntax style :(
>
>>
>> 2010/6/15 Otávio Pontes <otaviobp@gmail.com>:
>> > Hi,
>> > Last week i was working with adding to portage support for emerging
>> > packages from one specific repository.
>> > Atom class was modified to support a new field, with repository name.
>> > Now before package category it is possible to add a repository name
>> > followed by '::'.
>> > So emerge gentoo::app-portage/eix is the eix from repository gentoo.
>> > Atom class is already working, but emerge is still ignoring this
>> > repository name.
>> > It was also necessary to change other places in portage because slot
>> > separator is ':' and portage was getting confused when atom has '::'.
>> > This week work will be to use this atom information in portdbapi and
>> > in the dependency resolver to use ebuilds from the specified
>> > repository.
>> >
>> > Otávio
>> >
>> >
>>
>
>
> --
> Brian Dolbec <brian.dolbec@gmail.com>
>