From owner-freebsd-ports Sat Jun 5 6:10:30 1999 Delivered-To: freebsd-ports@freebsd.org Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (Postfix) with ESMTP id C0F3E14F70 for ; Sat, 5 Jun 1999 06:10:22 -0700 (PDT) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA22258; Sat, 5 Jun 1999 22:40:17 +0930 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA06374; Sat, 5 Jun 1999 22:41:19 +0930 Date: Sat, 5 Jun 1999 22:41:16 +0930 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Matt Behrens Cc: freebsd-ports@freebsd.org Subject: Re: SSH2 (in FreeBSD-Questions) In-Reply-To: Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 5 Jun 1999, Matt Behrens wrote: > : Patches accepted - actually, even just send-pr'ing a list of the broken ones > : would be more useful than just mentioning "ports in general". > : > : It's hard to fix what we don't know is broken. > > That I can understand. Please note also, though, the distinction > I make above with the packages that ignore command-line switches > -- I'm referring to the source tarballs themselves. A patch to > work around this broken behavior would be convoluted at best, I > would think. However, I'm certainly not going to just complain > and not do anything. I'll try to find the offenders again and make > patches. (Along those lines, I've noticed very few PLISTs contain > entries for manpages. Are they _supposed_ to?) Nope - they used to, but there were problems with manpages being gzipped, and being left around when the port was deinstalled. thesedays the manpage installation/deinstallation is taken care of via the MAN? variables and logic in bsd.port.mk > I've been mulling over solutions to this in my mind lately and > wonder if something along the lines of "/etc/paths.conf" or maybe > just another several lines in "/etc/make.conf" might be useful. > PREFIX works pretty well but it's limited to stuffing in a single > directory. I think the flexibility could be there to do something > The problem is that most software doesn't support such fine-grained installation control, and so in general you'd have to rework the build structure (and code) of the majority of ports. Not a small undertaking. Kris ----- "Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes." -- Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message