Date: Wed, 27 Mar 1996 19:24:12 -0800 (PST) From: "David E. O'Brien" <obrien@Nuxi.cs.ucdavis.edu> To: mike@sparc2.umeres.maine.edu (Mike Peck) Cc: ports@freebsd.org Subject: Re: TinyFugue 3.5a16 port uploaded Message-ID: <199603280324.TAA29837@relay.nuxi.com> In-Reply-To: <Pine.BSF.3.91.960323075707.11378A-100000@darkside.home> from "Mike Peck" at Mar 23, 96 08:01:02 am
next in thread | previous in thread | raw e-mail | index | archive | help
> I wrote a port of TinyFugue version 3.5a16 and put it in
> ftp.freebsd.org:/pub/FreeBSD/incoming as tinyfugue-35a16-port.tar.gz.
>
> This is my first port, so I'd appreciate it if someone could take
> a look at it and let me know if there's any problems.
I installed this port, and have a comment. Shouldn't the "library" files
go into .../share/tf-lib and not .../lib/tf-lb to be more inline with
hier(7)? I tracked down the place to change this in unix/Config. May I
also suggest making the "lib" dir name "tinyfugue" rather than tf to make
it easier to figure out what package the files go with.
On another note, it seems the ports were designed to allow one to install
to something other than /usr/local. I personally HATE them going into
/usr/local as that should be researved for MY local additions. I would
personally perfer /usr/pkg or something. Anyway that default location is
water over the dam.
BUT, shouldn't we port packages Makefile's so that they obey {PREFIX} (if
that is the right var)? Is PREFIX always passed down to other Makefile
from the port's Makefile?
-- David (obrien@cs.ucdavis.edu)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603280324.TAA29837>