Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Tue, 26 Oct 2004 19:17:45 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: perl vendor_perl/cygwin/Setup ? Message-ID: <20041026231745.GC3626@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <417EA1CD.2000703@x-ray.at> <417EC2CB.5060501@familiehaase.de> <018c01c4bba3$f2d7f880$e6ec6f83@robinson.cam.ac.uk> <417EC562.2030200@x-ray.at> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <417EC562.2030200@x-ray.at> User-Agent: Mutt/1.4.1i On Tue, Oct 26, 2004 at 11:45:06PM +0200, Reini Urban wrote: >Max Bowsher schrieb: >>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? > >well, why not? I do not want to release the upset perl modules. Neither they nor upset were written for general consumption. If I wanted to release them I'd be releasing them myself. cgf -- 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/