From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] dropbear: add extra build customization options
Date: Tue, 3 Feb 2015 20:30:19 +0100 [thread overview]
Message-ID: <20150203203019.153a2353@free-electrons.com> (raw)
In-Reply-To: <54D10B26.9000805@je-eigen-domein.nl>
Dear Floris Bos,
On Tue, 03 Feb 2015 18:53:42 +0100, Floris Bos wrote:
> > We'd however be open to merge the option to install or not the clients,
> > but we do have some comments/questions below.
> >
> >> +ifeq ($(BR2_PACKAGE_DROPBEAR_CLIENT),y)
> >> DROPBEAR_TARGET_BINS = dbclient dropbearkey dropbearconvert scp ssh
> >> DROPBEAR_MAKE = $(MAKE) MULTI=1 SCPPROGRESS=1 \
> >> PROGRAMS="dropbear dbclient dropbearkey dropbearconvert scp"
> >> -
> >> -DROPBEAR_LICENSE = MIT, BSD-2c-like, BSD-2c
> >> -DROPBEAR_LICENSE_FILES = LICENSE
> >> +else
> >> +DROPBEAR_TARGET_BINS = dropbearkey dropbearconvert scp
> >> +DROPBEAR_MAKE = $(MAKE) MULTI=1 SCPPROGRESS=1 \
> >> + PROGRAMS="dropbear dropbearkey dropbearconvert scp"
> >> +endif
> > Why is scp part of the server-only installation?
>
> Because scp is both a client and server program, similar to other
> programs that can tunnel data over SSH like rsync.
> When using scp on the client, it simply calls the ssh client program to
> connect to the SSH server and executes scp server-side there with a flag
> to tell it to play server and read further instructions/data from stdin,
> send data to stdout.
Ah, ok. Can you indicate that in the commit log, or maybe better, as a
comment in the code above the place where we defined what gets built
for the server-only case vs. server+client case?
> Do could make building scp a seperate Config.in option.
I don't think that's needed.
So, can you cook an updated patch?
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-02-03 19:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:43 [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Floris Bos
2014-09-11 15:43 ` [Buildroot] [PATCH 1/1] sqlite: add option to disable fsync Floris Bos
2014-09-11 21:53 ` Thomas Petazzoni
2014-09-13 21:51 ` Peter Korsgaard
2015-02-03 14:04 ` [Buildroot] [PATCH 1/1] dropbear: add extra build customization options Thomas Petazzoni
2015-02-03 17:53 ` Floris Bos
2015-02-03 19:30 ` Thomas Petazzoni [this message]
2015-02-04 15:35 ` Floris Bos
2015-02-04 15:40 ` Thomas Petazzoni
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=20150203203019.153a2353@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