Re: wrap-program –> wrap-script

2019-12-19 Thread Ludovic Courtès
Hello! Ricardo Wurmus skribis: > I’ve just pushed a change to use wrap-script in one package. The > purpose of wrap-script is to wrap an executable without having to create > a separate wrapper shell script. It does this by prepending a Guile > script to the top of the file, which sets the env

Re: wrap-program –> wrap-script

2019-12-17 Thread Ricardo Wurmus
Efraim Flashner writes: > On Wed, Dec 11, 2019 at 04:57:41PM +0100, Ricardo Wurmus wrote: […] >> I’ve just pushed a change to use wrap-script in one package. […] >> >> 2) we aren’t using wrap-script anywhere. I think a good use case would >> be the Python build system’s “wrap” phase where we

Re: wrap-program –> wrap-script

2019-12-17 Thread Efraim Flashner
On Wed, Dec 11, 2019 at 04:57:41PM +0100, Ricardo Wurmus wrote: > Hi Guix, > > I’ve just pushed a change to use wrap-script in one package. The > purpose of wrap-script is to wrap an executable without having to create > a separate wrapper shell script. It does this by prepending a Guile > scrip

Re: wrap-program –> wrap-script

2019-12-13 Thread Maxim Cournoyer
Hello Ricardo, Ricardo Wurmus writes: > Hi Guix, > > I’ve just pushed a change to use wrap-script in one package. The > purpose of wrap-script is to wrap an executable without having to create > a separate wrapper shell script. It does this by prepending a Guile > script to the top of the file

Re: wrap-program

2014-10-02 Thread Ludovic Courtès
Andreas Enge skribis: > I am only now catching up with the discussion. So far, I do not understand > why we need a wrapper. Would it not be enough to add the environment variables > $XDG_DATA_DIRS etc. to the search paths of the programs, in the same way as > perl or python modules incite the use

Re: wrap-program

2014-10-02 Thread Andreas Enge
Hello, I am only now catching up with the discussion. So far, I do not understand why we need a wrapper. Would it not be enough to add the environment variables $XDG_DATA_DIRS etc. to the search paths of the programs, in the same way as perl or python modules incite the user to define the correspo

Re: wrap-program

2014-09-27 Thread Federico Beffa
l...@gnu.org (Ludovic Courtès) writes: > Federico Beffa skribis: > >> 1. GSettings schemas: More than schemas compilation, the problem is that >> the schemas are by default expected to be in $datadir/glib-2.0/schemas >> (with $datadir usually being /usr/share). In spite of this, other >> directo

Re: wrap-program

2014-09-27 Thread Ludovic Courtès
Federico Beffa skribis: > 1. GSettings schemas: More than schemas compilation, the problem is that > the schemas are by default expected to be in $datadir/glib-2.0/schemas > (with $datadir usually being /usr/share). In spite of this, other > directories can be specified with the help of the envi

Re: wrap-program

2014-09-26 Thread Federico Beffa
On Fri, Sep 26, 2014 at 10:09 PM, Federico Beffa wrote: > l...@gnu.org (Ludovic Courtès) writes: > >> Mark H Weaver skribis: >> >>> This 'wrap-program' strategy of setting environment variables before >>> running a program has problems. In this case, it means that every >>> program run within Em

Re: wrap-program

2014-09-26 Thread Federico Beffa
l...@gnu.org (Ludovic Courtès) writes: > Mark H Weaver skribis: > >> This 'wrap-program' strategy of setting environment variables before >> running a program has problems. In this case, it means that every >> program run within Emacs will inherit that GSETTINGS_SCHEMA_DIR value. >> >> Along the