From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] mosh: new package
Date: Fri, 24 Jul 2015 08:14:26 +0300 [thread overview]
Message-ID: <20150724051425.GS13027@tarshish> (raw)
In-Reply-To: <1437688804-26537-1-git-send-email-christian@paral.in>
Hi Christian,
On Thu, Jul 23, 2015 at 03:00:04PM -0700, Christian Stewart wrote:
> diff --git a/package/mosh/Config.in b/package/mosh/Config.in
> new file mode 100644
> index 0000000..da5aa10
> --- /dev/null
> +++ b/package/mosh/Config.in
> @@ -0,0 +1,28 @@
> +
> +comment "mosh needs openssh and openssl to be built"
> + depends on !BR2_PACKAGE_OPENSSH || !BR2_PACKAGE_OPENSSL
> +
> +comment "mosh works on arm, i386, mipsel, or x64 architectures"
> + depends on BR2_arm || BR2_i386 || BR2_mipsel || BR2_x86_64
Target architecture dependency comments are not very helpful, since the user
can't do much about it is most cases. Moreover the other dependency comment
should only show when the target architecture is supported.
> +
> +comment "mosh needs a toolchain w/ threads"
> + depends on !BR2_TOOLCHAIN_HAS_THREADS
> +
> +comment "mosh needs a host architecture of x64 or x86"
> + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
> +
> +config BR2_PACKAGE_MOSH
> + bool "mosh"
> + depends on BR2_PACKAGE_OPENSSL
> + depends on BR2_PACKAGE_OPENSSH
I still think this two should be 'select'.
> + depends on BR2_TOOLCHAIN_HAS_THREADS
> + depends on BR2_arm || BR2_i386 || BR2_mipsel || BR2_x86_64
> + depends on BR2_HOSTARCH = "x86_64" || BR2_HOSTARCH = "x86"
> + select BR2_PACKAGE_PROTOBUF
> + select BR2_PACKAGE_NCURSES
> + help
> + Remote terminal application that supports intermittent connectivity,
> + allows roaming, and provides speculative local echo and line editing
> + of user keystrokes.
> +
> + https://github.com/keithw/mosh
> diff --git a/package/mosh/mosh.hash b/package/mosh/mosh.hash
> new file mode 100644
> index 0000000..1dfc1ba
> --- /dev/null
> +++ b/package/mosh/mosh.hash
> @@ -0,0 +1 @@
> +sha256 35025d412046ee5199ebaa8d876131fc683dccedde18b3945b3bc3662bc9f373 mosh-1.2.5.tar.gz
This doesn't match the hash mentioned at
https://github.com/keithw/mosh/releases/tag/mosh-1.2.5. This is most likely
due to your use of git checkout. Please use the official release tarballs,
either https://mosh.mit.edu/mosh-1.2.5.tar.gz or
https://github.com/keithw/mosh/releases/download/mosh-1.2.5/mosh-1.2.5.tar.gz.
Both match tag message hash.
> diff --git a/package/mosh/mosh.mk b/package/mosh/mosh.mk
> new file mode 100644
> index 0000000..1c58e05
> --- /dev/null
> +++ b/package/mosh/mosh.mk
> @@ -0,0 +1,16 @@
> +################################################################################
> +#
> +# mosh
> +#
> +################################################################################
> +
> +MOSH_VERSION = 1.2.5
> +MOSH_SITE = $(call github,keithw,mosh,mosh-$(MOSH_VERSION))
> +MOSH_DEPENDENCIES = zlib ncurses protobuf openssl
> +MOSH_LICENSE = GPLv3+
License exceptions?
> +MOSH_LICENSE_FILES = COPYING COPYING.iOS
> +
> +# Necessary as we are pulling from Git.
> +MOSH_AUTORECONF = YES
The official tarball should not need autoreconf.
> +$(eval $(autotools-package))
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-07-24 5:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 22:00 [Buildroot] [PATCH v4 1/1] mosh: new package Christian Stewart
2015-07-24 5:14 ` Baruch Siach [this message]
2015-07-24 7:07 ` Thomas Petazzoni
2015-07-24 12:40 ` Baruch Siach
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=20150724051425.GS13027@tarshish \
--to=baruch@tkos.co.il \
--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