Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Move openldap package and enable LDAP server?
Date: Fri, 4 Dec 2015 09:19:24 +0100	[thread overview]
Message-ID: <20151204091924.2f5f9c22@free-electrons.com> (raw)
In-Reply-To: <56614B18.4030703@gmx.de>

Hello,

On Fri, 4 Dec 2015 09:13:12 +0100, Andreas Ehmanns wrote:

> I was going to use openLDAP on my embedded device and found the 
> configuration under Target Packages -> Libraries -> Networking.
> You can enable openldap which only generates the ldap libraries but have 
> an option to let the client applications being built.
> Since I need the LDAP server I added an option to compile the LDAP 
> server too. Everything works fine and I thought about submitting the 
> patch but then I asked me if the configuration location is still the 
> right place.
> Wouldn't it be better to place the openldap configuration under
> Target Packages -> Networking Applications
> instead of
> Target Packages -> Libraries -> Networking
> 
> What is your opinion?

Yes, I agree that it probably makes more sense to have OpenLDAP in
Networking Applications, even if it indeed also provides a client
library.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-12-04  8:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-04  8:13 [Buildroot] Move openldap package and enable LDAP server? Andreas Ehmanns
2015-12-04  8:19 ` Thomas Petazzoni [this message]
2015-12-04  8:21   ` Andreas Ehmanns
2015-12-10 19:03     ` Andreas Ehmanns
2015-12-12 13:01       ` Thomas Petazzoni
2015-12-12 17:20         ` Andreas Ehmanns
2015-12-17 20:43         ` Andreas Ehmanns

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=20151204091924.2f5f9c22@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox