| 1 |
On 01/29/2015 06:02 PM, Zac Medico wrote: |
| 2 |
>> Nice logic here :) The only thing that I don't get is why we might need |
| 3 |
>> {provides,requires}_exclude patterns. I guess its good design |
| 4 |
>> principles but I can't think of a use case. |
| 5 |
> |
| 6 |
> I copied the idea from Fedora [2]. Since the soname dependencies are |
| 7 |
> automatically generated, we want to be able to filter them if necessary, |
| 8 |
> though hopefully it won't be needed very often. |
| 9 |
|
| 10 |
I've generated soname dependencies for all of the packages installed on |
| 11 |
my desktop system, and I'm using /etc/portage/profile/package.bashrc to |
| 12 |
set PROVIDES_EXCLUDE and REQUIRES_EXCLUDE for the packages that need it. |
| 13 |
I've put the settings in a git repo [1], so that people can see some |
| 14 |
examples of how PROVIDES_EXCLUDE and REQUIRES_EXCLUDE are useful. |
| 15 |
|
| 16 |
Typically, PROVIDES_EXCLUDE is useful for packages containing bundled or |
| 17 |
internal libraries. REQUIRES_EXCLUDE is useful for bundled or internal |
| 18 |
libraries that lack DT_SONAME, or to ignore soname references that are |
| 19 |
simply broken. |
| 20 |
|
| 21 |
[1] https://github.com/zmedico/portage-soname-bashrc |
| 22 |
-- |
| 23 |
Thanks, |
| 24 |
Zac |
Archives