Subject: Re: CVS commit: pkgsrc/mk/install
To: Roland Illig <rillig@NetBSD.org>
From: Alistair Crooks <agc@pkgsrc.org>
List: pkgsrc-changes
Date: 10/05/2006 19:57:27
On Thu, Oct 05, 2006 at 11:14:08AM +0200, Roland Illig wrote:
> >If the build/install infrastructure needs workarounds to accommodate
> >standalone-tcsh, then fine, put the workarounds in, but please don't
> >blame standalone-tcsh for the short-comings of another part of the
> >system.
> 
> It's not a shortcoming, but a convention that all programs are installed 
> into ${LOCALBASE}. There are only two packages that don't do so. 
> shells/standalone-tcsh and pkgtools/rc.subr. As noted in PR 33899 by 
> Joerg, it would be nice if all packages would honour LOCALBASE.

Tosh.

Long ago, we had ${X11BASE} and ${LOCALBASE}, and we made it so that
every package installed into ${LOCALBASE}, thereby preventing the
debasing of ${X11BASE}.

I'm not going to go into the whole saga of system packages, but if
they are to work, they need to be able to install into the root
filesystem.

One of the precepts of the standalone-tcsh package is that it installs
into /bin, and the pkgsrc infrastructure needs to be able to cope with
that - that's non-negotiable, no matter what any PR says.

I suggest that the root cause of the problem gets fixed, not the
symptoms.  Personally, I would have done:

.if ${PREFIX} != ${LOCALBASE}
CHECK_FILES_SUPPORTED= no
.endif

(or maybe .if ${PREFIX} == "/", I can't decide which) where it
mattered, rather than trying to tag package Makefiles.

Regards,
Alistair