[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: wrap-program –> wrap-script
From: |
Ludovic Courtès |
Subject: |
Re: wrap-program –> wrap-script |
Date: |
Thu, 19 Dec 2019 17:19:10 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Hello!
Ricardo Wurmus <address@hidden> 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 environment variables and
> then re-executes itself with the target interpreter (e.g. Python).
Neat!
> I noticed two things:
>
> 1) wrap-script does not automatically pull in Guile as a dependency, so
> if Guile isn’t among the inputs it will create a bad shebang. This
> should be fixed on core-updates.
Or we could say that it’s not different from other shebangs: it’s up to
the packager to provide all the necessary dependencies.
> 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 currently use
> wrap-program. Most of the time we’d be dealing with Python scripts, so
> using wrap-script would be more appropriate here.
The would immediately reach hundreds of packages, so it’s a good idea!
Thanks,
Ludo’.