Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Mar 2001 08:16:01 -0800 (PST)
From:      Matt Groener <root@groenquist.com>
To:        Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Cc:        joe@tao.org.uk, stable@FreeBSD.ORG, jqs@qad.com
Subject:   Re: Perl 5.6 merged soon?
Message-ID:  <Pine.BSF.4.21.0103160754580.96496-100000@joliet.groenquist.com>
In-Reply-To: <200103161541.KAA59453@khavrinen.lcs.mit.edu>

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


On Fri, 16 Mar 2001, Garrett Wollman wrote:

> In article <20010316133159.F2277@tao.org.uk> you write:
> 
> >That's what the new BSDPAN code is all about.  Making CPAN installs
> >accounted for in the system.
> 
> ``Accounted for'' is not particularly useful to me.  I don't use
> CPAN.pm anyway.
> 
> I know what most if not all of the modules are.  The problem is being
> required to figure out the dependency graph, recompile all of the
> modules in the right order, and then test all of my applications to
> ensure that they haven't been broken (because invariably, the module
> that I originally installed will have been superseded).  This is, to
> my mind, very much contrary to the spirit of ``stable''.

It would be "nice" if "perldoc perllocal" also reported dependencies
in addition to just locally installed modules, but I would suspect this
is a feature request for CPAN, and even then will not be of much use
to anyone until some time down the road when everyone is already in
sync.

You *can* use some muscle to keep updates in sync using CPAN if you
at least have the "perldoc perllocal" information handy:

1. Get all the tarballs of installed modules (based on "perldoc perllocal")
2. Untar them all, then loop through each Makefile.PL and look for:
	PREREQ_PM
   entries that tell the install what modules are required.
3. Go get those tarballs...
4. Rinse and repeat step two until you have all the dependencies
5. Reinstall them all with "force install" under CPAN or do it by hand

A completely different approach documented in the CPAN man page is to
use a Bundle definition (see Bundle::Slash in the CPAN tree for a good
example of this functionality). You can roll your own Bundle definition
for a box with minimal work (if you update it regularly as you install
more modules).

I will put in a "feature-request" to the CPAN maintainers to see if this
Bundle could be auto-built from within CPAN.

-matt


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0103160754580.96496-100000>