2014-07-27 23:33 Ciaran McCreesh napisał(a): > On Sun, 27 Jul 2014 17:26:27 -0400 > Rich Freeman <[email protected]> wrote: > > But, in that case you can put the necessary ebuilds into your overlay > > and then portage can make everything right. > > Oh? Please explain to us a) how the overlay interaction *actually* works > with dynamic dependencies currently
Portage uses dynamic dependencies from ebuild in original repository of given
installed ebuild.
Name of repository is stored in /var/db/pkg/${CATEGORY}/${PF}/repository file.
> and b) how it can work both in the case you describe
A user would have to do:
# echo ${new_repository} > /var/db/pkg/${CATEGORY}/${PF}/repository
# touch /var/db/pkg/${CATEGORY}/${PF}
# touch /var/db/pkg/${CATEGORY}
# touch /var/db/pkg
(It is possible that updating of timestamps is not yet strictly required...)
--
Arfrever Frehtes Taifersar Arahesis
signature.asc
Description: This is a digitally signed message part.
