Marius Feraru <altblue(a)n0i.net> writes:
Robin Norwood wrote:
> When we break the Requires on the other packages, we could add them to
> comps.xml alongside perl-devel. This way the default install would be
> 'all perl core modules', but one could easily remove the devel-related
> bits either at kickstart time (-<packagename> in the %packages section)
> or post-install.
"Default" ("base") install is already super-hyper-bloated. I'd
avoid
cluttering it even more.
Well, this isn't adding anything - we simply wouldn't be removing things
that, as Jose points out, are considered part of the core perl
distribution, and many people would be upset to find missing.
OTOH, you could go "classic", in a similar way like, for
instance, in order
to be able to build a gtk2 dependent app you need (among others) the
"gtk-devel" package.
So, you could alleviate this by adding (artificial) dependencies to the
"perl-devel" package in order to bring up *all* "core Perl"
packages.
For the current split status, this should feel quite ok, as all those
packages have a "developerish" nature:
%package devel
...
Requires: perl(CPAN)
Requires: perl(ExtUtils::Embed)
Requires: perl(ExtUtils::MakeMaker)
Requires: perl(Test::Harness)
Requires: perl(Test::Simple)
This is exactly what we're doing now (for f7), but I'd rather not have
artificial dependencies.
-RN
--
Robin Norwood
Red Hat, Inc.
"The Sage does nothing, yet nothing remains undone."
-Lao Tzu, Te Tao Ching