Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000701c48007$1b69c720$78d96f83@robinson.cam.ac.uk>
From: "Max Bowsher" <maxb AT ukf DOT net>
To: <cygwin AT cygwin DOT com>
References: <038701c47ff5$2506bc50$78d96f83 AT robinson DOT cam DOT ac DOT uk> <1042285252 DOT 20040812024734 AT familiehaase DOT de>
Subject: Re: Perl packaging suggestion - vendor_perl
Date: Thu, 12 Aug 2004 01:55:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
X-Cam-AntiVirus: No virus found
X-Cam-SpamDetails: Not scanned
X-IsSubscribed: yes
Note-from-DJ: This may be spam

Gerrit P. Haase wrote:
> Hallo Max,
>
> Am Donnerstag, 12. August 2004 um 00:47 schriebst du:
>
>> Would it be possible to package the extra modules included in the Cygwin
>> perl package in the vendor_perl hierarchy?
>
> Sure, this is obviously a good thing.

Thanks! I look forward to 5.8.6 or whatever.

>> This would leave the site_perl hierarchy clear for site additions, and
allow
>> site additions to be purged without affecting parts of the package.
>
> More interesting is that you can install your own version which goes
> to site_perl and overrides the distributed version in vendor_perl
> which is last path in the search order.

I've never understood that.

It seems to me that "site, vendor, core" would be a better order - to allow
core modules to be upgraded by a package. Or am I missing something?

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/