David O'Brien <[EMAIL PROTECTED]> types:
> On Sat, Dec 09, 2000 at 01:59:51PM -0600, Mike Meyer wrote:
> > I know. Unfortunately, support for PREFIX seems to draw more lip
> > service than actual service.
> I disagree. If one of the ports I maintain isn't PREFIX-clean, let me
> know and it _will_ be fixed. If you know others, please open a PR, let
> me know and I'll assign it to the maintainer.
Like I said, I do report them when I find them. However, things like
ports with perl modules being either PREFIX dirty or broken tend to be
pretty damning. But my comment is based on the experience of running a
system with LOCALBASE set to something other than /usr/local. If you
run systems that way and have a different experience, I'd be
interested in hearing about it.
> > or that the porters handbook should include instructions for checking
> > this (it's actually pretty easy),
> I always thought ``make PREFIX=/tmp/foo package'' is pretty obvious.. but
> maybe not...
It's not obvious to me. It's also not mentioned in the handbook
anywhere. I suspect that most people are like me, and seldomp build
packages - which would explain why it's not obvious. What does the
above command do if the port isn't PREFIX clean?
My personal test is "make PREFIX=/tmp/foo install && make
deinstall". If something in the plist is installed outside of
/tmp/foo, the deinstall will complain when it can't find it.
<mike
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
