1 |
2014-07-27 23:33 Ciaran McCreesh napisał(a): |
2 |
> On Sun, 27 Jul 2014 17:26:27 -0400 |
3 |
> Rich Freeman <rich0@g.o> wrote: |
4 |
> > But, in that case you can put the necessary ebuilds into your overlay |
5 |
> > and then portage can make everything right. |
6 |
> |
7 |
> Oh? Please explain to us a) how the overlay interaction *actually* works |
8 |
> with dynamic dependencies currently |
9 |
|
10 |
Portage uses dynamic dependencies from ebuild in original repository of given installed ebuild. |
11 |
Name of repository is stored in /var/db/pkg/${CATEGORY}/${PF}/repository file. |
12 |
|
13 |
> and b) how it can work both in the case you describe |
14 |
|
15 |
A user would have to do: |
16 |
# echo ${new_repository} > /var/db/pkg/${CATEGORY}/${PF}/repository |
17 |
# touch /var/db/pkg/${CATEGORY}/${PF} |
18 |
# touch /var/db/pkg/${CATEGORY} |
19 |
# touch /var/db/pkg |
20 |
|
21 |
(It is possible that updating of timestamps is not yet strictly required...) |
22 |
|
23 |
-- |
24 |
Arfrever Frehtes Taifersar Arahesis |