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] [PATCH 1/1 v3] package/unscd: new package
Date: Mon, 12 Oct 2015 18:42:02 +0200	[thread overview]
Message-ID: <20151012164202.GB3735@free.fr> (raw)
In-Reply-To: <20151012143542.GA21707@dkarchlinux64.gateway.pace.com>

Doug, MAxime, All,

On 2015-10-12 09:35 -0500, rdkehn at yahoo.com spake thusly:
> On Mon, Oct 12, 2015 at 10:34:09AM +0200, Maxime Hadjinlian wrote:
[--SNIP--]
> > nscd is a part of glibc, and looking at the code of glibc 2.22, the startup
> > script and systemd init file are included in the source. So I have a few
> > questions:
> > 
> > Why is this not a part of the glibc package as an option ?
> 
> ... good point.
> 
> I see glibc nscd (I'm using glibc 2.21) is built but not installed.
> Is the suggestion to add a nscd configuration option to glibc for
> native nscd or unscd?
> 
> If unscd is selected, only glibc nscd support files will be
> installed.

I would well see something along the lines of:

  - in toolchain/toolchain-common/in, add this:

    config BR2_GLIBC_NSCD
        bool "Install nscd"
        depends on BR2_TOOLCHAIN_USES_GLIBC

  - in package/unscd/Cofnig.in:

    config BR2_PACKAGE_UNSCD
        bool "unscd"
        depends on BR2_TOOLCHAIN_USES_GLIBC
        depends on !BR2_GLIBC_NSCD
        help
          unscd is a blabla replacement blabla...

          http://example.net/home/of/unscd

    comment "unscd needs an (e)glibc toolchain"
        depends on !BR2_TOOLCHAIN_USES_GLIBC

Note that we do not make BR2_GLIBC_NSCD an option of the glibc package,
because we also want to handle external toolchains. So it has to be a
toolchain option, not a package option.

Regards,
Yann E. MORIN.

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

  reply	other threads:[~2015-10-12 16:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09 14:10 [Buildroot] [PATCH 1/1 v3] package/unscd: new package Doug Kehn
2015-10-10 14:50 ` Yann E. MORIN
2015-10-12  8:34   ` Maxime Hadjinlian
2015-10-12 14:35     ` rdkehn at yahoo.com
2015-10-12 16:42       ` Yann E. MORIN [this message]
2015-10-12 16:34     ` Yann E. MORIN
2015-10-12 16:43       ` Yann E. MORIN
2015-10-13  7:38       ` Maxime Hadjinlian

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=20151012164202.GB3735@free.fr \
    --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