From: Andreas Enge <andreas@enge.fr>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: add kicad
Date: Thu, 4 Aug 2016 10:31:56 +0200 [thread overview]
Message-ID: <20160804083156.GA1684@solar> (raw)
In-Reply-To: <20160804015445.3c0d1615@scratchpost.org>
Hello,
On Thu, Aug 04, 2016 at 01:54:45AM +0200, Danny Milosavljevic wrote:
> > Unusual choice but I don't object to it. This would be the first package
> > to refer to libressl in our tree.
> We can also use openssl, I don't have a strong preference, really. Both projects seem to merge each other's security patches so we can also use openssl.
why not use libressl? We considered switching to it completely at some
point in time, but so far did not try it out. It would require an almost
complete rebuild in a testing branch, so maybe we should keep it in mind
and wait until the new machine is ready. So having one package that uses
it and builds with it could be a start.
This is independent of the question whether TLS support is actually needed
for this package :-)
Andreas
prev parent reply other threads:[~2016-08-04 8:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 7:40 [PATCH] gnu: add kicad Danny Milosavljevic
2016-02-15 11:35 ` Ben Woodcroft
2016-05-23 4:13 ` Leo Famulari
2016-07-07 0:22 ` Stuck on KiCad dependency wxPython Leo Famulari
2016-07-07 6:31 ` Efraim Flashner
2016-07-08 0:51 ` Leo Famulari
2016-07-08 10:15 ` Ricardo Wurmus
2016-07-12 9:24 ` Ludovic Courtès
2016-09-22 8:27 ` Danny Milosavljevic
2016-09-22 8:45 ` Danny Milosavljevic
2016-09-22 9:26 ` python-build-system: Allow build flags Danny Milosavljevic
2016-09-22 10:43 ` [PATCH] guix: python-build-system: Honor configure-flags also when building Danny Milosavljevic
2016-09-22 9:10 ` Stuck on KiCad dependency wxPython Danny Milosavljevic
2016-09-30 0:51 ` Theodoros Foradis
2016-09-30 7:09 ` Danny Milosavljevic
2016-08-03 23:54 ` [PATCH] gnu: add kicad Danny Milosavljevic
2016-08-04 8:31 ` Andreas Enge [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=20160804083156.GA1684@solar \
--to=andreas@enge.fr \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.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.