From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] ca-certificates: new package
Date: Fri, 10 Jan 2014 07:45:37 +0800 [thread overview]
Message-ID: <20140110074537.75d0a765@skate> (raw)
In-Reply-To: <1389201330-2420-1-git-send-email-martin@barkynet.com>
Dear Martin Bark,
On Wed, 8 Jan 2014 17:15:30 +0000, Martin Bark wrote:
> +config BR2_PACKAGE_CA_CERTIFICATES
> + bool "CA Certificates"
> + help
Indentation should be one tab.
> + This package includes PEM files of CA certificates to allow
> + SSL-based applications to check for the authenticity of SSL
> + connections.
And here one tab + two spaces.
> +
> + It includes, among others, certificate authorities used by the
> + Debian infrastructure and those shipped with Mozilla's browsers.
If possible, please add an upstream URL here.
> diff --git a/package/ca-certificates/ca-certificates.mk b/package/ca-certificates/ca-certificates.mk
> new file mode 100644
> index 0000000..6cf2e7a
> --- /dev/null
> +++ b/package/ca-certificates/ca-certificates.mk
> @@ -0,0 +1,39 @@
> +################################################################################
> +#
> +# ca-certificates
> +#
> +################################################################################
> +
> +CA_CERTIFICATES_VERSION = 20130906
> +CA_CERTIFICATES_SOURCE = ca-certificates_$(CA_CERTIFICATES_VERSION).tar.gz
> +CA_CERTIFICATES_SITE = $(BR2_DEBIAN_MIRROR)/debian/pool/main/c/ca-certificates
I think we should use snapshot.debian.net instead of BR2_DEBIAN_MIRROR.
Maybe we should even completely remove BR2_DEBIAN_MIRROR altogether.
The problem of using BR2_DEBIAN_MIRROR is that there is no guarantee
that the tarballs are going to stay at the same location, as Debian
evolves. While snapshot.debian.net guarantees this.
> +CA_CERTIFICATES_DEPENDENCIES = host-openssl host-python
> +CA_CERTIFICATES_LICENSE = GPLv2+ (script), MPLv2.0 (data)
> +CA_CERTIFICATES_LICENSE_FILES = debian/copyright
> +
> +define CA_CERTIFICATES_BUILD_CMDS
> + PATH=$(HOST_PATH) $(MAKE) -C $(@D) all
Instead of PATH=$(HOST_PATH), I'd prefer to see:
$(TARGET_MAKE_ENV) $(MAKE) -C $(@D) all
Also, the indentation of the command should be one tab.
> +endef
> +
> +define CA_CERTIFICATES_INSTALL_TARGET_CMDS
> + $(INSTALL) -d -m 0755 $(TARGET_DIR)/usr/share/ca-certificates
> + $(INSTALL) -d -m 0755 $(TARGET_DIR)/etc/ssl/certs
> + $(MAKE) -C $(@D) install DESTDIR=$(TARGET_DIR)
> + rm -f $(TARGET_DIR)/usr/sbin/update-ca-certificates
> +
> + #remove any existing certificates under /etc/ssl/certs
> + rm -f $(TARGET_DIR)/etc/ssl/certs/*
> +
> + #generate symlinks to certificates under /etc/ssl/certs
> + ( \
> + cd $(TARGET_DIR) ;\
> + for i in `find usr/share/ca-certificates -name "*.crt"` ; do \
> + ln -sf ../../../$$i etc/ssl/certs/`basename $${i%.crt}.pem` ;\
> + done ;\
> + )
This is not very pretty, but I don't really have a better suggestion,
unfortunately.
> +
> + #create symbolic links to the certificates by their hash values
> + $(HOST_DIR)/usr/bin/c_rehash $(TARGET_DIR)/etc/ssl/certs
> +endef
> +
> +$(eval $(generic-package))
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-09 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 17:15 [Buildroot] [PATCH v2] ca-certificates: new package Martin Bark
2014-01-09 23:45 ` Thomas Petazzoni [this message]
2014-01-10 14:23 ` Martin Bark
2014-01-10 23:43 ` Thomas Petazzoni
2014-01-09 23:59 ` Yann E. MORIN
2014-01-10 14:24 ` Martin Bark
2014-01-11 23:07 ` Yann E. MORIN
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=20140110074537.75d0a765@skate \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox