1 |
Kent Fredric <kentfredric@×××××.com> wrote: |
2 |
> |
3 |
> On 27 September 2013 05:57, Ciaran McCreesh |
4 |
><ciaran.mccreesh@××××××××××.com>wrote: |
5 |
> |
6 |
>> virtual/perl-* is self-inflicted. |
7 |
> |
8 |
> How would you recommend it? |
9 |
|
10 |
For those which are provided by perl itself, you could have |
11 |
a corresponding useflag of dev-lang/perl and make a use dependency: |
12 |
If the main perl tarball does not provide the package, the perl ebuild |
13 |
can pull in the corresponding package as a dependency. |
14 |
|
15 |
IMHO, virtual/perl-* are only useful when there are cases that |
16 |
a package must depend on a _particular version_ of that virtual: |
17 |
I considered it always strange that most of the perl packages are |
18 |
installed in duplicate only because the virtual version and the |
19 |
version provided by perl do not match. This is appropriate if |
20 |
something really needs a newer version, but not just because something |
21 |
*must* depend on the virtual only because some perl versions do |
22 |
not provide it. |