| 1 |
Am Sonntag, 14. April 2013, 15:09:13 schrieb Rich Freeman: |
| 2 |
> For whoever is interested I tossed together a script to identify |
| 3 |
> packages that would immediately benefit from slot operator |
| 4 |
> dependencies but which are not doing so. |
| 5 |
> |
| 6 |
> The list can be found at: |
| 7 |
> http://dev.gentoo.org/~rich0/missedslotops.txt |
| 8 |
> |
| 9 |
|
| 10 |
Please be careful with this... and think before you add the subslot |
| 11 |
dependency. Whether it makes sense depends a lot on the handling and on the |
| 12 |
maintainer of the package that you depend on. |
| 13 |
|
| 14 |
Examples (yes I learned...): |
| 15 |
|
| 16 |
1) Perl stuff |
| 17 |
I *suspect* all KDE ebuilds depend on perl by default because the packages |
| 18 |
have to be able to run perl scripts. However, unless they install perl modules |
| 19 |
or link to libperl, there is absolutely no need to add a subslot dependency. |
| 20 |
|
| 21 |
2) Poppler |
| 22 |
Poppler provides several libraries, and I set the subslot equal the major |
| 23 |
soversion of the one that is varied most frequently (libpoppler). |
| 24 |
If your application links to that, you should use a subslot dep. |
| 25 |
If your application links to another library, you can use a subslot dep, but |
| 26 |
it will lead to some unneeded rebuilds. |
| 27 |
If your application only uses the commandline tools installed by app- |
| 28 |
text/poppler[utils], then there's no need to rebuild. |
| 29 |
|
| 30 |
Actually I would like to recommend that we document the reason and recommended |
| 31 |
handling for the subslot somewhere for each package (unless it's trivial). For |
| 32 |
example, we could place something like the above text into dev-lang/perl or |
| 33 |
app-text/poppler metadata.xml. |
| 34 |
|
| 35 |
-- |
| 36 |
|
| 37 |
Andreas K. Huettel |
| 38 |
Gentoo Linux developer |
| 39 |
dilfridge@g.o |
| 40 |
http://www.akhuettel.de/ |
Archives