Date: Sat, 28 Feb 1998 17:55:27 -0500 (EST) From: Chuck Robey <chuckr@glue.umd.edu> To: "David E. O'Brien" <obrien@NUXI.com> Cc: Satoshi Asami <asami@FreeBSD.ORG>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/print/c2ps Makefile Message-ID: <Pine.BSF.3.96.980228175059.316V-100000@localhost> In-Reply-To: <19980228124306.44353@nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 28 Feb 1998, David E. O'Brien wrote: > > > 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, > > My points should be taken in a context where we don't change bsd.port.mk. > Tim's sugguestions are even better and superseed mine. > > > 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? > > Acutally I kinda like the idea of hacking the ports to look for a common > file that declares the prefered papersize. This means the same binary > works everywhere. Of course we could argue what the default should be > if that file is absent... :) Yeah, but how about the rest of the problem, ie., are there to be two (or more??) packages per port for ports that have USES_PAPERSIZE defined? At least the idea of doing it with a dropped cookie file removes the need for the per port cookie, and detecting a file during make is very easy to do. And how about naming conventions? You can see what my own position is by seeing what I did in a2ps, but I'm not particularly unwilling to use other's obviously good ideas. One last thing is that, if we _do_ decide on PAPERSIZE, then I thin we ought to ask Jordan to include such a thing in installation setup, and move the file into, perhaps, /etc or /etc/make.conf (as a defined var). > > -- > -- 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! ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980228175059.316V-100000>