Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <018c01c4bba3$f2d7f880$e6ec6f83@robinson.cam.ac.uk> From: "Max Bowsher" To: References: <417EA1CD DOT 2000703 AT x-ray DOT at> <417EC2CB DOT 5060501 AT familiehaase DOT de> Subject: Re: perl vendor_perl/Cygwin/Setup ? Date: Tue, 26 Oct 2004 22:37:04 +0100 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response 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: > Reini Urban wrote: > >> Gerrit, >> Shouldn't your next perl update also include our own perl libs? > > These are the libs required by upset? Indeed. Reini, why would you think these highly specialized modules are worth bundling in the main perl package? You could always ITP them seperately if you think that would be a useful thing to do. (Though you might have considerable difficulty getting +5 for them) 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/