1 |
On Tue, 2010-06-08 at 21:13 -0300, Otávio Pontes wrote: |
2 |
> Hi, |
3 |
> |
4 |
> I am writting my progress report for weeks 1 and 2. |
5 |
> My version of Portage is already loading repositories from repos.conf |
6 |
> and it’s still loading overlays from PORTDIR_OVERLAY. PORTDIR is still |
7 |
> the main repository, but it’s not necessary to set it in make.conf. |
8 |
> You can set that in repos.conf. I would like to change that, so we |
9 |
> will no longer need a main repository, but i think it will be too much |
10 |
> work, because PORTDIR variable is used all over portage code. PORTDIR |
11 |
> and PORTDIR_OVERLAY variables are updated with information loaded from |
12 |
> repos.conf, so it was easy to fix portage and other tools should work |
13 |
> without any changes. |
14 |
> |
15 |
> It's possible to set priorities for all repositories, even PORTDIR and |
16 |
> overlays, in repos.conf. The _local_repo_config class was replaced by |
17 |
> RepoConfigLoader and the code that used it in portdbapi is now using |
18 |
> directly this class. Treemap and _repository_map dicts in Portdbapi |
19 |
> are also no longer necessary because they are already defined in |
20 |
> RepoConfigLoader. So they are no longer created in portdbapi. |
21 |
|
22 |
|
23 |
Please keep them updated for now as they are used by consumer apps |
24 |
either directly or indirectly. It will require deprecation time to |
25 |
migrate to the new system. We will be implementing a new public API in |
26 |
portage that can be used as the primary access for consumer apps, but it |
27 |
will take time as it has not been coded yet, but will be in the next |
28 |
while. It will also need to be connected to your new repo support. |
29 |
|
30 |
> |
31 |
> My code is available in |
32 |
> git://git.overlays.gentoo.org/proj/portage-multirepo.git or in |
33 |
> overlays.gentoo gitweb. |
34 |
> |
35 |
> -- |
36 |
> Otávio Pontes |
37 |
> |
38 |
|
39 |
|
40 |
-- |
41 |
Brian Dolbec <brian.dolbec@×××××.com> |