| 1 |
On Mon, Mar 02, 2009 at 09:51:07AM -0800, Donnie Berkholz wrote: |
| 2 |
> On 13:08 Mon 02 Mar , Torsten Veller wrote: |
| 3 |
> > Currently the eclass doesn't set any dependencies. If it is used the |
| 4 |
> > ebuild has to depend on perl if needed. |
| 5 |
> > |
| 6 |
> > |
| 7 |
> > I see the following options: |
| 8 |
Perl modules by definition need dev-lang/perl installed to build |
| 9 |
(Makefile.PL is written in Perl). |
| 10 |
|
| 11 |
How many Perl modules can be installed with a Perl that is built with |
| 12 |
USE=build? |
| 13 |
|
| 14 |
> Having not spent a lot of time thinking about this, I'm guessing the use |
| 15 |
> case of concern is packages that have an optional perl module always |
| 16 |
> pulling in dev-lang/perl. This would apparently be relevant on an |
| 17 |
> embedded system that lacked perl but required a package with an optional |
| 18 |
> perl module. To handle that miniscule use case, I'd tend to go with a |
| 19 |
> conditional variable (GENTOO_PERL="no"?) that defaults to "yes". |
| 20 |
Yes, this would be needed in any case, similar to how it's done for |
| 21 |
stuff that had optional X dependencies. |
| 22 |
|
| 23 |
-- |
| 24 |
Robin Hugh Johnson |
| 25 |
Gentoo Linux Developer & Infra Guy |
| 26 |
E-Mail : robbat2@g.o |
| 27 |
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85 |
Archives