Doesn't seem to work on `busybox sh` for me (I am not aware of better way to
replicate POSIX environment on GNU Guix):
kreyren@leonid ~$ guix shell busybox -- busybox sh
...
~ $ cat test.sh
#!/usr/bin/env -S guix shell --
(use-modules
(guix channels))
(list (channel
(name 'guix
Hey Jacob,
On Tue, Nov 09 2021, Jacob Hrbek wrote:
For now I use “#!/usr/bin/env -S guix shell --”, which works
well enough for me. How does that sound? -- l...@gnu.org
Not a solution as (AFIAK) POSIX only accepts one argument.
That's the point of the -S. It passes the entire rest of the li
> For now I use “#!/usr/bin/env -S guix shell --”, which works well enough for
> me. How does that sound? -- l...@gnu.org
Not a solution as (AFIAK) POSIX only accepts one argument.
-- Jacob "Kreyren" Hrbek
Sent with ProtonMail Secure Email.
‐‐‐ Original Message ‐‐‐
On Tuesday, Novemb
Le 9 novembre 2021 13:01:46 GMT-05:00, zimoun a
écrit :
>Hi Ludo,
>
>On Tue, 09 Nov 2021 at 17:52, Ludovic Courtès wrote:
>> zimoun skribis:
>
>>> However, as I said elsewhere, this effort should start be collecting
>>> what do we consider as changes requiring formal process?
>>
>> Agreed, t
Hi,
On Tue, 09 Nov 2021 at 17:48, Ludovic Courtès wrote:
> What I think those figures show is the amount of manual tweaks necessary
> to get a proper package “à la Guix”, with tests running etc. For PyPI
> we often need to add things under ‘native-inputs’, hence the 71%
> “different inputs” lin
Hi Ludo,
On Tue, 09 Nov 2021 at 17:52, Ludovic Courtès wrote:
> zimoun skribis:
>> However, as I said elsewhere, this effort should start be collecting
>> what do we consider as changes requiring formal process?
>
> Agreed, that’s what I meant above.
I meant, based on changed already merged.
Ludovic Courtès, le mar. 09 nov. 2021 18:19:03 +0100, a ecrit:
> Am I right that the fixes have not been applied yet in the upstream
> repository?
That's right. That's still waiting for the copyright assignment.
Samuel
Hi Simon,
Simon Streit skribis:
> I am happy to announce the development of a Samba service for Guix.
>
> Currently I am attending a technical college for informatics where I am
> working on my final thesis that is due to be completed by February
> next year.
Nice!
> Hence I have already propo
Hi,
Jacob Hrbek skribis:
> I am unable to define a guix shell file with shebang to decrease the
> complexity needed in the repository managing (so
> that i can just do ./path/to/guix.scm for guix to invoke `guix shell -f
> ./path/to/guix.scm` instead of having to
> sanitize the runtime) as the
Hello,
Samuel Thibault skribis:
> Thanks a lot for this writing! That'll surely be an interesting read for
> whoever wants to look a bit at the details of how the Hurd works. And of
> course thanks for finding and fixing the vulnerabilities :)
Seconded. It’s interesting both from a security pe
Hello,
zimoun skribis:
> On Fri, 29 Oct 2021 at 16:12, Ludovic Courtès wrote:
[...]
>>> Well, because it is not affordable to switch from the current
>>> tag-address to immutable commit-address for defining packages, in order
>>> to be 100% reliable, any fallback should use Disarchive-DB whic
Hi,
zimoun skribis:
> On Fri, 29 Oct 2021 at 17:08, Ludovic Courtès wrote:
>
>> As zimoun wrote, a big question is formalization. I haven’t yet taken
>> the time to look at those other project RFC processes I mentioned, but
>> we should do that. Important questions are: how do we determine wh
Hi,
zimoun skribis:
> On Fri, 29 Oct 2021 at 23:57, Ludovic Courtès wrote:
[...]
>> --8<---cut here---start->8---
>> $ SAMPLE_SIZE=200 ./pre-inst-env guile
>> ~/src/guix-debugging/importer-accuracy.scm
>> […]
>> Accuracy for 'pypi' (200 packages):
>> acc
13 matches
Mail list logo
