From: "Nicolò Balzarotti" <anothersms@gmail.com>
To: Jelle Licht <jlicht@fsfe.org>, guix-devel@gnu.org
Subject: Re: Working on network-manager-l2tp
Date: Wed, 18 Mar 2020 13:51:11 +0100 [thread overview]
Message-ID: <87k13hkerk.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87mu8d7tw3.fsf@jlicht.xyz>
Jelle Licht <jlicht@fsfe.org> writes:
> Hey guix,
>
Hi!
> Seeing as a lot of people might be working from home at the moment, it
> seems a good moment to look at issues that might prevent us from using
> guix for that exact purpose. Right now, I can not connect to my company
> vpn, which make several processes much more difficult than they need to
> be.
>
> The issue with network-manager-l2tp is that because of licensing
> incompatibilities, version built with OpenSSL < 3.0 cannot be
> redistributed in binary form. As people informed me previously at [1],
> it seems that it is currently not possible to prevent the distribution
> of substitutes using guix.
>
I'm not 100% sure, but I saw a commit with zfs with the argument:
(#:substitutable? #f)
(it's under gnu/packages/file-systems.scm)
Maybe this is what you are looking for.
> I still would like to get network-manager-l2tp packaged, as well as make
> a simple service definition available. A hack that would allow us to
> truly disable substitutions of certain store paths is a
> solution. Another option is to simply wait until OpenSSL 3.0 is
> released, although this might still take until Q4 of 2020 [3].
>
> Any ideas?
>
> - Jelle
>
Nicolò
>
> [1]: http://logs.guix.gnu.org/guix/2019-10-15.log#171645
> [2]: https://github.com/nm-l2tp/NetworkManager-l2tp
> [3]: https://www.openssl.org/blog/blog/2019/11/07/3.0-update/
prev parent reply other threads:[~2020-03-18 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 12:02 Working on network-manager-l2tp Jelle Licht
2020-03-18 12:51 ` Nicolò Balzarotti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k13hkerk.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me \
--to=anothersms@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jlicht@fsfe.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.