Re: [PATCH 1/4] gnu: Add XFILESEARCH path to profiles' environment.

[John Darrington <john@darrington.wattle.id.au>]

[-- Attachment #1: Type: text/plain, Size: 2231 bytes --]

On Tue, Nov 29, 2016 at 10:42:49PM +0100, Ludovic Court??s wrote:
     John Darrington <john@darrington.wattle.id.au> skribis:
     
     >      > * Hack the hard coded defaults in the libXt source to use the profile
     >      > settings instead of /usr
     >      
     >      Maybe we should just do that, no?  It???d be a local change, it would
     >      achieve the same effect, and it would provide a good default.
     >      
     >
     > It sounds unreliable to me.  What would we set it to?
     > $GUIX_PROFILE/...  $HOME/.guix-profile/... /run/current-system/profile/...
     > There's no guarantee that the current profile is any of those.
     
     Maybe, but that would have the same effect as setting the environment
     variable to that value, wouldn???t it?

Except that the environment variable solution is easier for users to override. 
     
     > Something similar to the first solution seems prefereable to me.  Maybe:
     >
     >  Set XFILESEARCHPATH to "$HOME/.guix-profile/lib/X11/%T/%N%S:/run/current-system/profile/lib/X11/%T/%N%S"
     >   (we can substitute "share" for "lib" if we want to keep the FHS people happy).
     
     How did you manage to shorten it that much?  

Simply by assuming that nobody ever installs resource files outside these locations.
If anybody ever does - then things will break.
     
     >  Then we audit all users of libxt to make sure they put their resource files in lib/X11/app-defaults.
     >  Most packages have a --with-app-defaults configure option (which currently we are in many cases
     >  either not using or misusing).
     >
     >  We could also consider adding a build stage to make sure that packages which depend on libXt put
     >  their resource files in the "right" place.
     
     Sounds reasonable.

All in all, it sounds like a lot of work in the short time - but it might be worth it.
I'll see what I can do (and if it has a chance of working).

J'
     

-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]