From: "Adrian Bunk" <bunk@stusta.de>
To: Vyacheslav Yurkov <uvv.mail@gmail.com>
Cc: Openembedded-core@lists.openembedded.org, tmark@isc.org,
Vyacheslav Yurkov <Vyacheslav.Yurkov@bruker.com>
Subject: Re: [OE-core] [PATCH] dhcp: use included bind version
Date: Wed, 10 Jun 2020 20:42:20 +0300 [thread overview]
Message-ID: <20200610174220.GE24380@localhost> (raw)
In-Reply-To: <15e11034-2d2b-a620-f859-450a2b7ef7de@gmail.com>
On Wed, Jun 10, 2020 at 06:31:55PM +0200, Vyacheslav Yurkov wrote:
> On 10.06.2020 18:07, Adrian Bunk wrote:
> > On Wed, Jun 10, 2020 at 04:35:20PM +0200, Vyacheslav Yurkov wrote:
> > > ...
> > > BIND9 libraries support a lot of options specifically geared towards
> > > optimizing DNS operations, many of which do not play nicely with
> > > ISC DHCP's "architecture". It isn't necessarily practical to build
> > > those libraries for both purposes.
> > > ...
> > Providing security support for several different copies of the BIND
> > code would be a nightmare.
> >
> > cu
> > Adrian
>
> Right, but I don't think there's a way to build two configurations out of
> one recipe, isn't it?
It is possible.
More common is sharing the sources between two (or more) recipes
with an .inc file.
Unrelated to that, I am a bit suprised why the current Yocto setup
is suddenly a problem. Other distributions like Debian/Ubuntu are
also sharing one build of the BIND libraries between BIND and dhcpd.
> Vyacheslav
cu
Adrian
next prev parent reply other threads:[~2020-06-10 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 14:35 [PATCH] dhcp: use included bind version Vyacheslav Yurkov
2020-06-10 15:02 ` ✗ patchtest: failure for " Patchwork
2020-06-10 15:05 ` [OE-core] [PATCH] " Richard Purdie
2020-06-10 16:36 ` Vyacheslav Yurkov
2020-06-13 0:41 ` Khem Raj
2020-06-13 8:31 ` Vyacheslav Yurkov
2020-06-17 10:35 ` Alexander Kanavin
2020-06-10 16:07 ` Adrian Bunk
2020-06-10 16:31 ` Vyacheslav Yurkov
2020-06-10 17:42 ` Adrian Bunk [this message]
2020-06-10 18:40 ` Vyacheslav Yurkov
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=20200610174220.GE24380@localhost \
--to=bunk@stusta.de \
--cc=Openembedded-core@lists.openembedded.org \
--cc=Vyacheslav.Yurkov@bruker.com \
--cc=tmark@isc.org \
--cc=uvv.mail@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