1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA1 |
3 |
|
4 |
Jorge Manuel B. S. Vicetto wrote: |
5 |
> This seems desirable and reasonable. |
6 |
> As I replied to this subject earlier regarding KDE, let me complement |
7 |
> that information. In the case of the KDE team, we keep work on a release |
8 |
> all in the same place, so we don't need to unmask some KDE packages in |
9 |
> tree for those using the overlay. However, we some times have deps on |
10 |
> packages from other teams and or in other overlays, so I hope the repo |
11 |
> deps would help here (not to unmask those packages, if they're masked, |
12 |
> but to add a dep on a particular repo and allowing the PM explain to the |
13 |
> user that he/she needs to unmask a particular version in the tree / |
14 |
> overlay). |
15 |
|
16 |
The problem with repo deps is that they're too restrictive since |
17 |
they assume that only a specific repo can satisfy the dep. Suppose |
18 |
that you migrate some of the packages from the overlay to the main |
19 |
tree? Now you've got installed packages that are trying to pull in |
20 |
deps from the wrong repo. Or suppose that somebody else has an |
21 |
overlay with a compatible package? |
22 |
|
23 |
I think a better way to reference another repo is with the |
24 |
layout.conf approach suggested in the "QA Overlay Layout support" |
25 |
thread [1]. For example, if packages from the java-experimental repo |
26 |
depend on some ebuilds or eclasses from the java-overlay repo, it's |
27 |
specified via a "masters" entry in layout.conf. If any of those |
28 |
ebuilds/eclasses happen to migrate to the main tree then the |
29 |
migration is seamless. |
30 |
|
31 |
[1] |
32 |
http://archives.gentoo.org/gentoo-dev/msg_33c61550b4ed2b7b25dd5a4110e1ec81.xml |
33 |
- -- |
34 |
Thanks, |
35 |
Zac |
36 |
-----BEGIN PGP SIGNATURE----- |
37 |
Version: GnuPG v2.0.10 (GNU/Linux) |
38 |
|
39 |
iEYEARECAAYFAkmvMcIACgkQ/ejvha5XGaNmkwCePw/XjWCqZtIXq5yXQ4gpHALL |
40 |
fXUAoMqkmJ30Go2SJaqS2lzs+8axyLwn |
41 |
=ju66 |
42 |
-----END PGP SIGNATURE----- |