Date: Thu, 17 Aug 1995 18:06:15 -0700 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: Chris Haidinyak <chrish@alpha.techspecs.com> Cc: agc@uts.amdahl.com, ports@freebsd.org Subject: Re: Postgres95 for FreeBSD Message-ID: <22092.808707975@time.cdrom.com> In-Reply-To: Your message of "Thu, 17 Aug 1995 11:24:54 PDT." <199508171824.LAA09228@alpha.techspecs.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> It sounds like agc@uts.amdahl.com is also working to finish the port > of postgres95 to FreeBSD. I personally haven't done any work on the port; > it has been nicely done already. What I did find out was that the version > of lex (flex) FreeBSD distributes is out-of-date. Other than that the package > compiled quite nicely. The only reason I am asking it be put onto the officia Again, as I said, all we need are whatever diffs or build procedures are necessary to building and *installing* the port and we can do the whole thing as a FreeBSD port. /usr/ports/databases has only 2 entries in it, and it'd sure be nice to have more than that! Putting something into the ports collection also has the added value of _advertising_ the port. There's really no use in porting something if people aren't able to easily find out about it, and the ports collection is very well advertised with even a WEB interface to it now available (http://freefall.freebsd.org/Ports). The only downside is that it takes just a little more work to make a "port" out of something since you're essentially seeking to automate the entire process. A user should be able to: cd /usr/ports/databases/postgres95 make all install And have it all happen automagically from there. Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?22092.808707975>