Subject: Re: problem with the STk package
To: None <firstname.lastname@example.org>
From: Perry E. Metzger <email@example.com>
Date: 07/02/1998 18:12:27
That won't work for me. The binaries have the paths coded in. They
also use the same string for figuring out platform dependent
behavior. Changing the string used would be painful.
Tim Rightnour writes:
> On 02-Jul-98 Perry E. Metzger spoke unto us all:
> # The package pretty much insists on hard coding the architecture into
> # the build directory, which makes the PLIST non-MI. I tried several
> # trivial ways to fix this, and it turns out that the package knows way
> # too much way too deeply about the name of said directory -- it is
> # hardcoded into a couple of things.
> I don't really understand what you are asking here.. but I'll take a stab at
> it. On my glunix pkg, it does a very annoying thing and names the binaries
> (and slews of directories and the like) xxxx-i386-NetBSD. (or alpha, or
> whatever) so you end up with platform dependent install targets, and it screw
> up the plist, blah blah blah..
> I fixed it by having "make" call make install inside the work tree, it instal
> into a subdir of the work tree, and then the make install target of the pkg
> makefile does a *real* install, and moves all the files, and renames them and
> all that fun stuff.
> Tim Rightnour - firstname.lastname@example.org