Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] package/libcamera: Add libcamera package
Date: Tue, 19 Mar 2019 16:38:23 +0100	[thread overview]
Message-ID: <20190319153823.GB2702@scaer> (raw)
In-Reply-To: <940dcdca-91e1-9460-35f7-782959a7ad02@ideasonboard.com>

Kieran, All,

On 2019-03-19 14:12 +0000, Kieran Bingham spake thusly:
> On 19/03/2019 12:50, Yann E. MORIN wrote:
> > On 2019-03-19 11:03 +0000, Kieran Bingham spake thusly:
> >> diff --git a/DEVELOPERS b/DEVELOPERS
> >> index c91325e28486..5bcdf208a62b 100644
> >> --- a/DEVELOPERS
> >> +++ b/DEVELOPERS
> >> @@ -1260,6 +1260,9 @@ F:	package/ramsmp/
> >>  N:	Kevin Joly <kevin.joly@sensefly.com>
> >>  F:	package/libgphoto2/
> >>  
> >> +N:	Kieran Bingham <kieran.bingham@ideasonboard.com>
> >> +F:	package/libcamera/
> Is it possible to put the libcamera mailinglist as a 'cc' target here as
> well? or is it only individuals.

The problem is that libcamera-dev is subscription-based too, so people
who are not subscribed get a "pending-approval" message, which is not
very interesting...

> If someone (other than me) updates the package, It would be nice for
> that notification to go to the list.

Well, the goal of the DEVELOPERS file is that someone-not-you update the
package, they do Cc you. For example, with your patch applied, run:

    ./utils/get-developers -p libcamera

Or:

    git show |./get-developers -

which will reprt you as the person to Cc on patches touching the
libcamera package.

> > Also, as you already discovered, it's nice to pass a new package through
> > utils/test-pkg as well (and although not mandatory, it's nice to provide
> > that report after the --- line.)
> 
> I was going to ask how to do this - as it was skipping all 6, and then
> all 43 toolchains with -a. But I've worked it out, so for the benefit of
> others:

From the manual:

    https://buildroot.org/downloads/manual/manual.html#_tips_and_tricks

    17.23.3. How to test your package

> I had to create a libcamera.config and specify the EUDEV dependency:
> 
>   BR2_ROOTFS_DEVICE_CREATION_DYNAMIC_EUDEV=y
>   BR2_PACKAGE_LIBCAMERA=y
> 
> Then:
>  ./utils/test-pkg -c libcamera.config -p libcamera

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-03-19 15:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-19 11:03 [Buildroot] [RFC PATCH] package/libcamera: Add libcamera package Kieran Bingham
2019-03-19 11:25 ` Kieran Bingham
2019-03-19 12:50 ` Yann E. MORIN
2019-03-19 14:12   ` Kieran Bingham
2019-03-19 15:38     ` Yann E. MORIN [this message]
2019-03-20  9:39       ` Kieran Bingham
2019-03-19 23:18     ` Arnout Vandecappelle
2019-03-20  9:25       ` Kieran Bingham
2019-03-20  9:29         ` Yann E. MORIN
2019-03-20  9:43           ` Kieran Bingham
2019-03-20  9:34         ` Arnout Vandecappelle
2019-03-20  9:42           ` Kieran Bingham

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=20190319153823.GB2702@scaer \
    --to=yann.morin.1998@free.fr \
    --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