mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Bruno Thomsen <bth@kamstrup.com>
To: "m.olbrich@pengutronix.de" <m.olbrich@pengutronix.de>
Cc: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] [PATCH] curl: install root CA certificates option
Date: Fri, 16 Jan 2015 11:10:43 +0000	[thread overview]
Message-ID: <915054555B5659448ACF8A70E114824D0186C007DE@Exchange2010.kamstrup.dk> (raw)
In-Reply-To: <20150112162108.GM26436@pengutronix.de>


Hi Michael

Thanks for feedback. I have created 2 new patches that address the issues you have found.

> > +$(STATEDIR)/libcurl.extract:
> > +	@$(call targetinfo)
> > +	@$(call clean, $(LIBCURL_DIR))
> > +	@$(call extract, LIBCURL, $(BUILDDIR))
> > +	@$(call patchin, LIBCURL, $(LIBCURL_DIR))
> > +ifdef PTXCONF_LIBCURL_CA_BUNDLE
> > +	@$(LIBCURL_DIR)/lib/mk-ca-bundle.pl -i -d$(MOZ_CA_TREE) -v $(LIBCURL_DIR)/ca-bundle.crt
> > +endif
>
> No, not like this. Downloading an undefined version of a file during the
> build process is not acceptable.
>
> Add a second file to download (see rules/host-tz-database.make) how to do
> this) and use a URL that does not change, maybe the last tag:
> http://hg.mozilla.org/releases/mozilla-release/raw-file/FIREFOX_35_0_RELEASE/security/nss/lib/ckfw/builtins/certdata.txt

I have create a new host "certificate bundle downloader"-package (rules/host-certdata.make).

> Also, you need to 'select HOST_SYSTEM_PERL' in the .in file and running
> mk-ca-bundle.pl should be in the compile stage. Otherwise the dependencies
> are not handled correctly.

I have add dependency on HOST_SYSTEM_PERL and HOST_CERTDATA if LIBCURL_CA_BUNDLE is selected.
Moved mk-ca-bundle.pl call from extract to compile stage.

Bruno



-- 
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2015-01-16 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  8:04 Bruno Thomsen
2015-01-12 16:21 ` Michael Olbrich
2015-01-16 11:10   ` Bruno Thomsen [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=915054555B5659448ACF8A70E114824D0186C007DE@Exchange2010.kamstrup.dk \
    --to=bth@kamstrup.com \
    --cc=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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