From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <ptxdist-bounces@pengutronix.de>
Received: from mail-wi0-x233.google.com ([2a00:1450:400c:c05::233])
	by metis.ext.pengutronix.de with esmtp (Exim 4.72)
	(envelope-from <alex.aring@gmail.com>) id 1YL5mU-0004m1-3l
	for ptxdist@pengutronix.de; Tue, 10 Feb 2015 09:02:50 +0100
Received: by mail-wi0-f179.google.com with SMTP id hi2so1725811wib.0
	for <ptxdist@pengutronix.de>; Tue, 10 Feb 2015 00:02:44 -0800 (PST)
Date: Tue, 10 Feb 2015 09:02:39 +0100
From: Alexander Aring <alex.aring@gmail.com>
Message-ID: <20150210080238.GA21110@omega>
References: <1423551921-29670-1-git-send-email-oliver.graute@neuhaus.de>
	<20150210075318.GA19979@omega>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20150210075318.GA19979@omega>
Subject: Re: [ptxdist] [PATCH] added mosh package to ptxdist
Reply-To: ptxdist@pengutronix.de
List-Id: PTXdist Development Mailing List <ptxdist.pengutronix.de>
List-Unsubscribe: <http://metis.pengutronix.de/cgi-bin/mailman/options/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=unsubscribe>
List-Archive: <http://metis.pengutronix.de/pipermail/ptxdist>
List-Post: <mailto:ptxdist@pengutronix.de>
List-Help: <mailto:ptxdist-request@pengutronix.de?subject=help>
List-Subscribe: <http://metis.pengutronix.de/cgi-bin/mailman/listinfo/ptxdist>, 
	<mailto:ptxdist-request@pengutronix.de?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ptxdist-bounces@pengutronix.de
Errors-To: ptxdist-bounces@pengutronix.de
To: ptxdist@pengutronix.de
Cc: Oliver Graute <oliver.graute@neuhaus.de>

Hi,

I missed something, please add also a name before your mail subject
like:

[PATCH] mosh: added mosh package to ptxdist

On Tue, Feb 10, 2015 at 08:53:18AM +0100, Alexander Aring wrote:
> Hi,
> 
> I have also some rules for mosh, but I added IPv6 support on it (which
> is available on the github master branch).
> Nevertheless I have some issues with mosh and IPv6 and that was the
> reason why I didn't send it mainline. I try to compare now my rule with
> your rule.
> 
> On Tue, Feb 10, 2015 at 08:05:21AM +0100, Oliver Graute wrote:
> > added a rule for mosh 
> > 
> > Signed-off-by: Oliver Graute <oliver.graute@neuhaus.de>
> > ---
> >  rules/mosh.in   |    7 ++++
> >  rules/mosh.make |  102 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> >  2 files changed, 109 insertions(+)
> >  create mode 100644 rules/mosh.in
> >  create mode 100644 rules/mosh.make
> > 
> > diff --git a/rules/mosh.in b/rules/mosh.in
> > new file mode 100644
> > index 0000000..1866a4d
> > --- /dev/null
> > +++ b/rules/mosh.in
> > @@ -0,0 +1,7 @@
> > +## SECTION=networking
> > +
> > +config MOSH
> > +	tristate
> > +	prompt "mosh"
> 
> In my rule file I have:
> 
> 	select PROTOBUF
> 	select NCURSES
> 	select ZLIB
> 	select OPENSSL
> 
> Additional I detected (because installing the mosh perl script):
> 
> 	select PERL
> 	select IO_SOCKET_IP_PERL

this should all if RUNTIME, because it's only necessary if you running
the mosh script at runtime.

If you don't want to install the mosh script, maybe we could add a own
config there. Something like "config MOSH_INSTALL_MOSH_SCRIPT".

> 	select OPENSSH			if RUNTIME
> 	select OPENSSH_SSH		if RUNTIME
> 	select OPENSSH_SSHD		if RUNTIME
> 

.....

> > +#MOSH_CONF_OPT	:= $(CROSS_AUTOCONF_USR)
> > +
> 
> #
> # autoconf
> #
> MOSH_AUTOCONF	:= \
> 	$(CROSS_AUTOCONF_USR) \
> 	--enable-hardening \
> 	--enable-client \
> 	--enable-server \
> 	--disable-examples \
> 	--enable-ufw \

the ufw is some ubuntu firewall helper thingy. Better to disable it
here. We don't have such fancy stuff. :-)

- Alex

-- 
ptxdist mailing list
ptxdist@pengutronix.de