Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gnupg: ensure deterministic build by disabling libcurl
Date: Tue, 10 Jul 2012 11:26:13 -0700	[thread overview]
Message-ID: <4FFC73C5.4080207@linux.intel.com> (raw)
In-Reply-To: <CAMKF1sr7U+mDi=5c2_C9ejW05DBQzHCY6RYoWr_L4xB3KKuYUQ@mail.gmail.com>

On 07/09/2012 06:21 PM, Khem Raj wrote:
> On Mon, Jul 9, 2012 at 4:45 PM, Saul Wold <sgw@linux.intel.com> wrote:
>> On 07/09/2012 03:43 PM, Khem Raj wrote:
>>>
>>> On Mon, Jul 9, 2012 at 3:04 PM, Saul Wold <sgw@linux.intel.com> wrote:
>>>>
>>>> gnupg has it's own fake curl, since we use gnupg with zypper, there does
>>>> not
>>>> seem to be a strong reason to add curl to the depends list.
>>>
>>>
>>> what does disabling curl has to do with gnupg being used with zypper ?
>>>
>> I was looking for where gnupg was used within oe-core and it's usage model
>> to see if it made sense to go with the extra dependency for gnupg, let me
>> know your reasoning.  Generally especially for natives we look for ways to
>> reduce the initial build time.
>
> I am all for it. I wanted to understand the context thanks for that.
> On another note
Do you want me to amend the commit message?


> it would be interesting to know what are we losing if we disable curl
> or external curl
>
gnupg seems to use a very small subset of curl and the curl_shim that it 
provides covers what's need in a very basic manner (including handling 
proxy setups).  I would guess (after a cursory look) that we would lose 
better error handling and performance for the gpgkeys_curl command line 
interface.

I think that acceptable.

Sau!

>>
>> Sau!
>>
>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>>
>>
>




  reply	other threads:[~2012-07-10 18:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-09 22:04 [PATCH] gnupg: ensure deterministic build by disabling libcurl Saul Wold
2012-07-09 22:43 ` Khem Raj
2012-07-09 23:45   ` Saul Wold
2012-07-10  1:21     ` Khem Raj
2012-07-10 18:26       ` Saul Wold [this message]
2012-07-10 18:52         ` Khem Raj

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=4FFC73C5.4080207@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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