cvs commit: ports CHANGES UPDATING ports/Mk bsd.port.mk ports/accessibility/linux-atk Makefile pkg-plist ports/archivers/stuffit Makefile ports/astro/linux-setiathome Makefile ports/audio/baudline Makefile ports/audio/linux-arts ...

[Dejan Lesjak]

On Tuesday 28 of June 2005 20:32, David O'Brien wrote:
> On Tue, Jun 28, 2005 at 01:52:05PM +0200, Dejan Lesjak wrote:
> > On Monday 27 of June 2005 19:01, David O'Brien wrote:
> > > On Sat, Jun 25, 2005 at 07:24:20PM +0200, Michael Nottebrock wrote:
> > > > On Saturday, 18. June 2005 00:59, Alexander Leidinger wrote:
> > > > >     - Use the correct prefix (X11- instead of LOCAL- or LINUX-) for
> > > > > some ports. Chase dependencies for this.
> > > >
> > > > I know I'm late to the party, but I'm really wondering what that is
> > > > meant to accomplish.
> > > >
> > > > X_PREFIX is *not* the 'correct' prefix for *anything* but the X11
> > > > distribution
> > >
> > > Not quite.  Anything that uses Imake will also be installed in
> > > X_PREFIX. If that's not what we desire, we should fix
> > > /usr/X11R6/lib/config.
> >
> > Or Imakefiles of those ports can be changed. Or parameters passed to
> > imake can be changed. I'd prefer that to actually modifying imake
> > configuration if possible and if modifying imake-using ports wouldn't
> > turn out too complicating.
>
> No the philisphy behind Imake is that a package doens't have to know
> site-specific policy - it is suppose to be encoded in the site-specific
> Imake configuration.

Yes, but in this case a port that does not override imake cf defaults expects 
to be installed in same place as X11 - basically under ProjectRoot as defined 
by imake configuration (as imake specifies prefix for it).
DESTDIR for example is respected by imake and ports can set it (like for 
example astro/sunclock does). Furthermore BINDIR, MANDIR and such are also 
respected by Makefiles that imake generates so they can be simply overridden 
by MAKE_FLAGS.
The point is that we are actually overriding default prefix of something when 
it is converted to port. The same way --prefix=${PREFIX} is added to 
CONFIGURE_ARGS for GNU_CONFIGURE case so I believe it would be consistent to 
do it this way.

> What is wrong with installing proper site configuration files?

Mostly that this would also change default prefix for Xorg/XFree so they would 
also install under that different prefix (unless of course we'd build X with 
either custom imake config files or with custom flags). Which would actually 
be good if eventually it is decided to have a common prefix for all ports 
(like, say, pkgsrc with /usr/pkg). Perhaps that wouldn't be such a bad 
idea...

Perhaps I'm just overcomplicating. Did you have some specific imake config 
change in mind?

Dejan