All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] libgphoto2: Add libgphoto2 package
Date: Fri, 7 Apr 2017 22:52:11 +0200	[thread overview]
Message-ID: <d0b4e258-3c24-2691-3d93-03c4f1a936e8@gmail.com> (raw)
In-Reply-To: <cd88fd7c-dceb-cef1-59de-e086c6b3df00@sensefly.com>

Hi Kevin, Thomas,

Le 07/04/2017 ? 07:14, Kevin JOLY a ?crit :
> Hello Thomas,
> 
> I was talking with Romain on this mailing list and he had concern about license
> and dependencies of libgphoto2. I contacted the developpers of libgphoto2 to
> ensure that the license type was correct. I also turned the libexif, jpeg and gd
> dependencies as optional.
> 
> Anyway, if the patch is in the pipe, everything is fine. I re-submitted it
> because I didn't saw it was already on patchwork but I didn't wanted to be
> redundant with it.

Indeed, I've posted a patch adding libgphoto2 in Buildroot some day before your
initial submission [1], but it's ok since you're working on it.

It would be great if you add a small changlog between each iteration, see [2]
(21.5.4. Patch revision changelog). That's why Thomas asked what changed in your
last submission.

Also, can you check this new package with the new test-pkg script ? [3]
(17.20.2. How to test your package).

I'll review it later this week-end.
I'll mark my initial patch superseded in the patchwork.

Best regards,
Romain

[1] http://patchwork.ozlabs.org/patch/735448/
[2] http://nightly.buildroot.org/manual.html#submitting-patches
[3] http://nightly.buildroot.org/manual.html#_tips_and_tricks
> 
> Thank you
> 
> Kevin JOLY
> 
> Le 06. 04. 17 ? 22:36, Thomas Petazzoni a ?crit :
>> Hello,
>>
>> On Thu, 6 Apr 2017 10:33:12 +0200, Kevin JOLY wrote:
>>> Add support for libgphoto2 core library designed to allow access to digital camera.
>>>
>>> Signed-off-by: Kevin JOLY <kevin.joly@sensefly.com>
>>> ---
>>>  DEVELOPERS                         |  3 +++
>>>  package/Config.in                  |  1 +
>>>  package/libgphoto2/Config.in       | 11 +++++++++++
>>>  package/libgphoto2/libgphoto2.hash |  6 ++++++
>>>  package/libgphoto2/libgphoto2.mk   | 29 +++++++++++++++++++++++++++++
>>>  5 files changed, 50 insertions(+)
>>>  create mode 100644 package/libgphoto2/Config.in
>>>  create mode 100644 package/libgphoto2/libgphoto2.hash
>>>  create mode 100644 package/libgphoto2/libgphoto2.mk
>> Thanks for this patch. However:
>>
>>  - You already posted a patch for the same package on March, 13th, but
>>    you don't explain how this version is different. This patch is not
>>    even identified as a new iteration. What changed?
>>
>>  - Romain Naour submitted on March 5 a patch adding libgphoto2, so your
>>    proposal seems a bit redundant with Romain's patch. Have you taken
>>    over Romain's patch? I'm adding Romain in Cc here.
>>
>> Thanks!
>>
>> Thomas
> 
> -- 
> 
> *Kevin JOLY*
> Embedded systems engineer
> 
> SenseFly <http://www.sensefly.com/>
> 38, rte de Gen?ve
> 1033 Cheseaux-Lausanne, Switzerland
> 
> 
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 

  reply	other threads:[~2017-04-07 20:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:33 [Buildroot] [PATCH 1/1] libgphoto2: Add libgphoto2 package Kevin JOLY
2017-04-06 20:36 ` Thomas Petazzoni
2017-04-07  5:14   ` Kevin JOLY
2017-04-07 20:52     ` Romain Naour [this message]
2017-04-10  9:24       ` Kevin JOLY
2017-04-10 11:45         ` Thomas Petazzoni
2017-04-10 12:01           ` Arnout Vandecappelle
2017-04-10 10:20 ` Arnout Vandecappelle
2017-04-10 12:23   ` Kevin JOLY
2017-04-10 13:28     ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2017-03-13  7:26 Kevin JOLY
2017-03-08 13:38 Kevin JOLY
2017-03-08 20:10 ` Romain Naour
2017-03-09  6:52   ` Kevin JOLY
2017-03-16 23:17     ` Romain Naour
2017-04-06  8:31       ` Kevin JOLY

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=d0b4e258-3c24-2691-3d93-03c4f1a936e8@gmail.com \
    --to=romain.naour@gmail.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.