On Fri, 17 Jan 2003 23:14:04 +0700, verily did Robert Elz write:

>| Relatively easy to have packages use ${PKGROOT}/lib/X11/app-defaults,
>| instead.

> Is it?   Isn't most of that stuff done via regular Xlib calls?   And
> Xlib knows nothing about ${PKGROOT} (or ${LOCALBASE} or similar).

You are referring to Xlib calls that follow ${XAPPLRESDIR}, which I've
already covered.  I wasn't referring to that, I was referring to file
placement upon "make install".

>   | Asking someone to put ${PKGROOT}/lib/X11/app-defaults in their
>   | ${XAPPLRESDIR} (and ${XFILESEARCHPATH} for Solaris) is barely worse

> It is much worse.   Most people understand PATH and can appreciate what
> it is for,   Just looking at the XAPPLRESDIR name is enough to send those
> same people off the edge...

"just like PATH, but for app-defaults" is a fairly simple statement, any
way you slice it.

If someone goes over the edge on that, they need to go back to MacOS9.
(Not that I'm bagging on MacOS9, I still use it.)

>   | than asking them to put ${PKGROOT}/bin in their ${PATH}.

> Which no-one needs to do anyway.   Just typing /usr/pkg/bin/bash
> works just fine.   But XAPPLRESDIR isn't like that.

Ah yes, everyone types /path/to/my/binary, all the time.


> The union mount of app-defaults is (IMNSHO) easily the best way to
> handle this, and with "mount -o hidden" it remains essentially invisible
> to the masses, and everything just plain works.

So you're telling us that "mount the foo filesystem union on top of the bar
filesystem with the `hidden' flag" is easier for users
than "set XAPPLSRESDIR to /usr/pkg/lib/X11/app-defaults"?

heh.

Rob++
----------------------------------------
Internet: windsor@warthog.com                             __o
Life: Rob@Carrollton.Texas.USA.Earth                    _`\<,_
                                                       (_)/ (_)
The weather is here, wish you were beautiful.