Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com Message-ID: <3CC9B75C.3090308@ece.gatech.edu> Date: Fri, 26 Apr 2002 16:23:56 -0400 From: Charles Wilson 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: "Larry Hall (RFK Partners, Inc)" CC: "Gerrit P. Haase" , Jan Nieuwenhuizen , cygwin-apps AT cygwin DOT com Subject: Re: ITP: netpbm References: <87r8l2pf8w DOT fsf AT peder DOT flower> <87r8l2pf8w DOT fsf AT peder DOT flower> <4 DOT 3 DOT 1 DOT 2 DOT 20020426153847 DOT 02c89b08 AT pop DOT ma DOT ultranet DOT com> <4 DOT 3 DOT 1 DOT 2 DOT 20020426160426 DOT 02ca4c28 AT pop DOT ma DOT ultranet DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Larry Hall (RFK Partners, Inc) wrote: > They can be accommodated by providing a > script with the package that moves the files elsewhere if this becomes a big > issue, no? upgrades? Also, user customized installations belong in /usr/local; don't mess with /usr if you want support from the list. I'd probably end up ignoring Jan's package and rebuilding my own version (which goes into: /usr/local/bin/netpbm/* /usr/local/lib/ /usr/local/include/ etc... Or maybe downloading Jan's -src package with each new release and rebuilding it after changing the prefix...and the /bin/netpbm/ ... --Chuck