ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2002/04/26/15:53:51

Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Message-ID: <3CC9B043.3020805@ece.gatech.edu>
Date: Fri, 26 Apr 2002 15:53:39 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: "Gerrit P. Haase" <freeweb AT nyckelpiga DOT de>
CC: cygwin-apps AT cygwin DOT com
Subject: Re: ITP: netpbm
References: <87r8l2pf8w DOT fsf AT peder DOT flower> <3CC998A6 DOT 3030104 AT ece DOT gatech DOT edu> <3CC99AFC DOT 4080009 AT ece DOT gatech DOT edu> <1371249928832 DOT 20020426204512 AT familiehaase DOT de>

Gerrit P. Haase wrote:

>>Okay, *two* more things: you may want to package this "the right way"
>>from the beginning -- and avoid the pain I (and everyone else by proxy) 
>>went thru.  Split out your DLLs from everything else and have two 
>>packages...'netpbm' and 'libpnmXX'.  That way, when user bob builds 
> Ohoh, that makes me nervous...
> If a new perl package gets released I probably should also release a
> 'libperl-5.6.1' package which contains only the libperl-5.6.1.dll ?

Probably not - and here's why:  (1) the DLLs are already versioned down 
to the micro level (2) anybody cluefull enough to actually build 
something against the perl DLL is cluefull enough to save the DLL 
version they need for their private package 'foo' before upgrading perl.

Actually, given the interdependencies in /usr/lib/perl5/5.6.1/...  I 
don't think the DLL is much use, without all the other stuff under 

So, in the case of perl, I don't think it makes much sense to split the 
DLL from the rest of the package.  OTOH, allowing two perls to coexist 
might be a reasonable thing...perhaps the parrot should be released as 
'perl6-6.x.y' and not 'perl-6.x.y'.


- Raw text -

  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019