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] [PATCH] Rename netkitbase and netkittelnet
Date: Sat, 14 Dec 2013 18:32:32 +0100	[thread overview]
Message-ID: <20131214183232.04cea60b@skate> (raw)
In-Reply-To: <CACjG4B+HvDwZ-SQ8QE0oSH2zd7tZF73=T=4ayYHqg-GW4GMDKg@mail.gmail.com>

Dear arnaud aujon,

On Fri, 13 Dec 2013 18:51:45 +0100, arnaud aujon wrote:
> Ok, so netkitbase provides 2 binaries : inetd which can be replaced by
> xinetd and ping that is provided by busybox (is there another package
> providing it ?)

There is iputils, but we don't have a package for it in Buildroot (I
have one in a private branch, just haven't had the time to clean it up
to upstream it). It provides, amongst others, the full-featured ping
implementation.

> For netkittelnet, again busybox provides a telnet client.
> So Config.in.legacy should be updated by something like that :
> 
> config BR2_PACKAGE_NETKITBASE
>     bool "netkitbase has been removed"
>     select BR2_LEGACY
>     help
>       The 'netkitbase' package has been removed, since it
>       has been deprecated since 2012.11. This package provided  'inetd'
> which
>       is replaced by 'xinet' and 'ping' which is replaced by 'busybox' or
> 'fping'.
> 
> config BR2_PACKAGE_NETKITTELNET
>     bool "netkittelnet has been removed"
>     select BR2_LEGACY
>     help
>       The 'netkittelnet' package has been removed, since it
>       has been deprecated since 2012.11. 'busybox' provides a telnet client
> and
>       should be used instead.
> 
> But should we automatically select a replacement or let the user decide
> what to do ?

Normally, we select things automatically, when there is a direct match.
In this case, I believe there isn't really a direct complete match, so
I would personally suggest to not select something automatically.

Best regards,

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

      reply	other threads:[~2013-12-14 17:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-24  8:55 [Buildroot] [PATCH] Rename netkitbase and netkittelnet Arnaud Aujon
2013-10-24 13:34 ` Thomas Petazzoni
2013-10-24 14:58   ` arnaud aujon
2013-12-03  8:47     ` arnaud aujon
2013-12-03  9:01       ` Thomas Petazzoni
2013-12-13 17:51         ` arnaud aujon
2013-12-14 17:32           ` Thomas Petazzoni [this message]

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=20131214183232.04cea60b@skate \
    --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