1 |
On Tue, 2010-06-15 at 19:42 +0200, Auke Booij wrote: |
2 |
> Paludis actually puts the repository name after the package, for |
3 |
> example app-portage/eix::gentoo. Is there any specific reason you |
4 |
> decided to do it your way? I don't know how pkgcore does this, btw, |
5 |
> just interested to hear your reasoning. |
6 |
> |
7 |
> tulcod. |
8 |
|
9 |
|
10 |
Yes pkgcore is the same repo syntax as paludis. So why mess with a |
11 |
standard the other 2 package mangers have had for a few years already? |
12 |
It'll be confusing as hell for users trying to figure out and keep |
13 |
straight between PM's and forum postings saying one way, then another. |
14 |
Also for someone like me coding a gui frontend it means having 2 |
15 |
different code blocks to do the same thing, one for each syntax style :( |
16 |
|
17 |
> |
18 |
> 2010/6/15 Otávio Pontes <otaviobp@×××××.com>: |
19 |
> > Hi, |
20 |
> > Last week i was working with adding to portage support for emerging |
21 |
> > packages from one specific repository. |
22 |
> > Atom class was modified to support a new field, with repository name. |
23 |
> > Now before package category it is possible to add a repository name |
24 |
> > followed by '::'. |
25 |
> > So emerge gentoo::app-portage/eix is the eix from repository gentoo. |
26 |
> > Atom class is already working, but emerge is still ignoring this |
27 |
> > repository name. |
28 |
> > It was also necessary to change other places in portage because slot |
29 |
> > separator is ':' and portage was getting confused when atom has '::'. |
30 |
> > This week work will be to use this atom information in portdbapi and |
31 |
> > in the dependency resolver to use ebuilds from the specified |
32 |
> > repository. |
33 |
> > |
34 |
> > Otávio |
35 |
> > |
36 |
> > |
37 |
> |
38 |
|
39 |
|
40 |
-- |
41 |
Brian Dolbec <brian.dolbec@×××××.com> |