Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 16 Oct 2004 10:56:36 +0200
From:      Erwin Lansing <erwin@FreeBSD.org>
To:        perl@FreeBSD.org
Subject:   Re: Reduce dependency for p5-WWW-Mechanize*
Message-ID:  <20041016085635.GA42564@droso.net>
In-Reply-To: <4170E055.3020503@thegler.dk>
References:  <7mr7o07q1x.wl@black.imgsrc.co.jp> <4170E055.3020503@thegler.dk>

next in thread | previous in thread | raw e-mail | index | archive | help

--vEao7xgI/oilGqZ+
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Oct 16, 2004 at 10:48:21AM +0200, Lars Thegler wrote:
> Jun Kuriyama wrote:
> >Hi again, :-)
> >
> >More dependency reducing here:
>=20
> While I understand the motivation for dependency reduction, I have a=20
> feeling that, in the case of Perl modules, this is the wrong direction=20
> to go. I agree, that for instance, Pod::Parser v1.14 is currently=20
> included in lang/perl5.8. But what should happen, when this module is=20
> updated on CPAN, and textproc/p5-PodParser is updated? IMHO, the user=20
> would want the module to be updated. But if there is no dependency, the=
=20
> port is not installed, and the module is not updated. I agree, that we=20
> can remove the dependency now, but then we should reinsert it when=20
> textproc/p5-PodParser is updated, and I do not see that happening ;)
>=20
<rant>
This is exactly the reason why I think it was a major mistake of the
perl people to include even more and more modules in the distribution. A
year or so ago, I spend a huge amount of time trying to conditionalise
the dependencies for modules now included in 5.8, only to find out that
this might not be the best solutions after all. Modules should be
modules, not distribution!
</rant>

I agree with Lars that this is a non-trivial issue. The modules now
included in the distribution, don't stand still and other modules are
going to depend on newer version of those, that are not in the
distribution. Adding and removing the dependency depending on if the
module has a newer version on CPAN than in the distribution might be the
techinically best solution, but it's practically infeasible. I think
that the best way is to keep the dependency, as long as it doesn't
overwrite files from the distribution.

Cheers,
-erwin

--=20
                    _._     _,-'""`-._
Erwin Lansing      (,-.`._,'(       |\`-/|    erwin@lansing.dk
http://droso.org       `-.-' \ )-`( , o o)    erwin@FreeBSD.org
                    -bf-      `-    \`_`"'-

--vEao7xgI/oilGqZ+
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBcOJDqy9aWxUlaZARAoVvAKCumGgaz/zqmzOrZRr7t1zK3piDtACg1L9X
ABGePcpmlD/TkoBBI+Z4gXY=
=2MXS
-----END PGP SIGNATURE-----

--vEao7xgI/oilGqZ+--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041016085635.GA42564>