From owner-cvs-ports Sat Feb 28 11:47:31 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11367 for cvs-ports-outgoing; Sat, 28 Feb 1998 11:47:31 -0800 (PST) (envelope-from owner-cvs-ports) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11357; Sat, 28 Feb 1998 11:47:26 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id OAA19860; Sat, 28 Feb 1998 14:46:37 -0500 (EST) Date: Sat, 28 Feb 1998 14:46:37 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: "David E. O'Brien" cc: Satoshi Asami , cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/print/c2ps Makefile In-Reply-To: <19980228100355.30619@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-ports@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 28 Feb 1998, David E. O'Brien wrote: > > If you do that, the many folks who download a single port will have it > > fail on them. These are the same folks who wouldn't understand why. The > > gain? This is a smallish port, so about a thousand bytes. > > Good point by Chuck. Maybe we should keep the current a2ps port as the > "guts" of the port, and add two shell ports, being a2ps-a4 and > a2ps-letter. Might be less confusion for someone that doens't use the > ports collection often. David, I'm not entirely sure what you mean by that, I might or might not agree. Some points made by Tim are valid, I think ... PAPERSIZE is, I think all will agree, a commonly enough used variable to where handling by bsd.port.mk is reasonable, the only question in my mind left to be resolved is how any change in bsd.port.mk would meld with the packaging mechanism. I would lean toward an adaptation (via bsd.port.mk) of the cookie idea that's in the current a2ps, but that is somewhat likely to be because I wrote that, so take the recommendation with a grain of salt (that means I'm obviously biased towards my own software). Tim, you brought up the idea of doing it in bsd.port.mk. Any more thoughts? Does anyone else think the cookie notion stinks, or how else would you handle packaging? > > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------