From owner-cvs-ports Thu Oct 24 02:30:06 1996 Return-Path: owner-cvs-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA05978 for cvs-ports-outgoing; Thu, 24 Oct 1996 02:30:06 -0700 (PDT) Received: from pillar.elsevier.co.uk (root@pillar.elsevier.co.uk [193.131.222.35]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA05864; Thu, 24 Oct 1996 02:29:33 -0700 (PDT) Received: from snowdon.elsevier.co.uk (snowdon.elsevier.co.uk [193.131.197.164]) by pillar.elsevier.co.uk (8.8.2/8.8.0) with ESMTP id KAA21045; Thu, 24 Oct 1996 10:26:36 +0100 (BST) Received: from cadair.elsevier.co.uk by snowdon.elsevier.co.uk with SMTP (PP); Thu, 24 Oct 1996 10:28:54 +0100 Received: from tees.elsevier.co.uk (tees.elsevier.co.uk [193.131.197.60]) by cadair.elsevier.co.uk (8.8.2/8.8.0) with ESMTP id KAA20450; Thu, 24 Oct 1996 10:28:49 +0100 (BST) Received: (from dpr@localhost) by tees.elsevier.co.uk (8.8.2/8.8.0) id KAA17258; Thu, 24 Oct 1996 10:27:45 +0100 (BST) To: James FitzGibbon Cc: CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-ports@freefall.freebsd.org Subject: Re: cvs commit: ports/databases/p5-DBI - Imported sources References: <199610232352.QAA20667@freefall.freebsd.org> From: Paul Richards Date: 24 Oct 1996 10:27:45 +0100 In-Reply-To: James FitzGibbon's message of Wed, 23 Oct 1996 16:52:53 -0700 (PDT) Message-ID: <57iv80vhim.fsf@tees.elsevier.co.uk> Lines: 41 X-Mailer: Gnus v5.3/Emacs 19.30 Sender: owner-cvs-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk James FitzGibbon writes: > Log Message: > Import of module for generic access to databases in perl5. > > Status: > > Vendor Tag: CPAN > Release Tags: v0_73 You've obviously spent a lot of time working on this and that is appreciated but I've got some concerns. First, in reference to this particular set of ports, I'd much rather have had all those modules be in the same part of the tree as Perl5 itself. Generally I don't know that a perl module exists for some task I'm going to try or at best I've a package name that someone's mentioned but I don't know much about it. Until now, I've just connected to a CPAN site and looked around because they were all in the same place. Maybe it's just me, but I'm never going to find half of these modules because they're in places I'm just not going to think to look. A perl_module or CPAN port would have been much better. It would also have made tracking CPAN and these modules much, *much* easier. The second point is more general and relates to what should actually go into ports. Having a bug chunk of CPAN in the "sparse template" system we have will actually be quite neat but the cdrom is going to have to have all the distfiles as well. Maybe we should set out guidelines about what we actually import since it's not going to be practical to import the entirety of all the archive sites in the world into ports. Personally, although it's very nice to have it there, I think things like CPAN are better served by Perl specific cdroms and distributions, likewise all the lisp packages for emacs, all the tex macros etc. -- Paul Richards. Originative Solutions Ltd. (Netcraft Ltd. contractor) Elsevier Science TIS online journal project. Email: p.richards@elsevier.co.uk Phone: 0370 462071 (Mobile), +44 (0)1865 843155