From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/xmlsec1: new package
Date: Sat, 13 Apr 2019 22:38:39 +0200 [thread overview]
Message-ID: <20190413223839.65cd4e0e@windsurf> (raw)
In-Reply-To: <CACHoAdpicM=WcFLCgcPoose_qx8Kcig-_sD6fN8uMTJmWuLCtg@mail.gmail.com>
Hello Bastian,
On Tue, 12 Feb 2019 17:13:08 +0100
Bastian Breit <bastian.breit.buildroot@gmail.com> wrote:
> I would summit options with later commits for the dependencies like
> gnutls which is currently deactivated for this package. Should that be
> mentioned in the help text? It should be clear by reading the current
> dependencies.
We don't typically document all possible dependencies of packages in
the help text, it would be annoying to maintain. Handling them in
the .mk file is enough.
> Does anyone prefer gnutls over openssl for non licencing
> reasons? I am not sure how to handle licence changing by selecting
> different dependencies (gnutls vs openssl)
Why would the license change ? The license of libxmlsec1 itself remains
MIT.
I guess that openssl/gnutls/libgcrypt is actually a choice, i.e one
would use one of the three, correct ?
If so, then you can do:
select BR2_PACKAGE_OPENSSL if !BR2_PACKAGE_GNUTLS && !BR2_PACKAGE_LIBGCRYPT
in the Config.in file, and:
ifeq ($(BR2_PACKAGE_OPENSSL),y)
LIBXMLSEC1_DEPENDENCIES += openssl
LIBXMLSEC1_CONF_OPTS += --with-openssl=$(STAGING_DIR)/usr
else ifeq ($(BR2_PACKAGE_GNUTLS),y)
...
else ifeq ($(BR2_PACKAGE_LIBGCRYPT),y)
...
endif
You could also do the same to support libxslt as an optional
dependency. All of this can be done as part of the initial libxmlsec1
submission, or as follow-up patches.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-04-13 20:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 15:12 [Buildroot] [PATCH v2] package/xmlsec1: new package Bastian Breit
2019-02-12 16:13 ` Bastian Breit
2019-04-13 20:38 ` Thomas Petazzoni [this message]
2019-02-16 12:53 ` Bastian Breit
2019-04-13 20:35 ` Thomas Petazzoni
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=20190413223839.65cd4e0e@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.
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.