Verily did "Mark W. Eichin" write:

>> That's right, and quite useful. But sometimes you have some
>> harwired paths wich depend on the prefix you choose. Thats why I

> Just to make it clear: the hardwired paths depend on the prefix you
> gave to *configure*, not to make install. If you do
> 	configure --prefix /usr/local/bsd/opt/gnu
> 	make
> and then
> 	make prefix=/tmp/pkgbuild/usr/local/bsd/opt/gnu install
> you can tar up stuff from inside /tmp/pkgbuild and it will have the
> /usr/local/bsd/opt/gnu paths compiled in (in whatever cases that would
> happen.)

I agree.

I fear that those who are debating with me have misunderstood my e-mail.
The apps that I compile can reside -anywhere- on your filesystem.  Just
make sure that you have symlinks in /usr/local/{bin,lib,man,foo} that
point to the appropriate files. (e.g. the apps only think that they
are sitting in /usr/local/bin).

I mentioned /usr/local/install because that's where I keep things, since
it's easy to NFS mount /usr/local and have things work painlessly that way.

If someone wants to grab my packages and throw them in /usr/pkgs and
symlink from /usr/local/bin to /usr/pkgs/xemacs/bin (an example), then
it will work.

*sigh*

-- Rob
----------------------------------------
Internet: windsor@pobox.com      Life: Rob@Sunnyvale.California.USA.Earth
"Da Web": http://pobox.com/~windsor/

"Ain't much distance 'tween a pat on the back and a kick in the pants."
    -- David Lee Roth (1990), `The Dogtown Shuffle'