Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Woody Douglass <wdouglass@carnegierobotics.com>
Cc: "fontaine.fabrice@gmail.com" <fontaine.fabrice@gmail.com>,
	"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] package/opencv4: add support for opencv4_contrib repository for extra modules
Date: Thu, 3 Nov 2022 23:50:20 +0100	[thread overview]
Message-ID: <20221103235020.70bb8e8e@windsurf> (raw)
In-Reply-To: <70a53e0eb3fdc514641a9cb83dd42aa5bd0f1be6.camel@carnegierobotics.com>

Hello Woody,

On Thu, 3 Nov 2022 22:30:21 +0000
Woody Douglass <wdouglass@carnegierobotics.com> wrote:

> This adds a separate opencv4_contrib package to manage
> downloading/unpacking that repository. These extra modules
> are useful for a lot of applications, but not necessary
> for minimal installs, so they are all given dedicated Kconfig
> options
> 
> Signed-off-by: Woodrow Douglass <wdouglass@carnegierobotics.com>

Thanks a lot for your patch! One issue is that because you did not send
it with "git send-email", it arrived on the mailing list badly damaged
(line-wrapped)  by your e-mail client.

Also, one thing that really should be explained in the commit log is
that the opencv4-contrib is only useful to download additional source,
but that it actually gets built as part of the opencv4 package itself,
which is why opencv4-contrib is a dependency of opencv4 and not the
other way around.

Even though this is quite unusual, it should be noted that it is not
the first case we have: nginx modules are handled in the same way
(see nginx-upload, nginx-dav-ext, nginx-naxsi, nginx-modsecurity).

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-11-03 22:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 22:30 [Buildroot] [PATCH 1/1] package/opencv4: add support for opencv4_contrib repository for extra modules Woody Douglass via buildroot
2022-11-03 22:50 ` Thomas Petazzoni via buildroot [this message]
2022-11-03 23:06   ` Woody Douglass via buildroot
  -- strict thread matches above, loose matches on Subject: below --
2022-11-04 12:20 Woody Douglass via buildroot
2022-11-16 12:46 ` Woody Douglass via buildroot
2022-11-17 17:34 Woodrow Douglass via buildroot
2022-11-20  9:37 ` Yann E. MORIN
2022-11-20 22:32   ` Woody Douglass via buildroot
2022-11-21 17:20     ` 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=20221103235020.70bb8e8e@windsurf \
    --to=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=wdouglass@carnegierobotics.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