From: Jon Turney <jon.turney@dronecode.org.uk>
To: Libor Ukropec <ace@seznam.cz>,
"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] picocom 3.1
Date: Sat, 7 Jan 2023 13:26:03 +0000 [thread overview]
Message-ID: <5d5a1cb9-0633-3eb8-7eea-5ab4b9c3f7eb@dronecode.org.uk> (raw)
In-Reply-To: <e14237ad-2c27-a17b-6fdb-c48aeaa65c39@seznam.cz>
On 03/01/2023 23:02, Libor Ukropec via Cygwin-apps wrote:
> ackage name
> NAME="picocom"
> VERSION=3.1
> RELEASE=1
>
> # .hint generation
> CATEGORY="Utils"
> SUMMARY="Minimal dumb-terminal emulator"
> DESCRIPTION="picocom was designed to serve as a simple, manual, modem
> configuration, testing, and debugging tool. It has also served (quite
> well) as a low-tech \"terminal-window\" to allow operator intervention
> in PPP connection scripts (something like the ms-windows \"open
> terminal window before / after dialing\" feature). It could also prove
> useful in many other similar tasks. It is ideal for embedded systems
> since its memory footprint is minimal."
> HOMEPAGE="hhttps://github.com/npat-efault/picocom"
There seems to be typo here (a doubled h in hhttps)
> LICENSE="GPL-2.0"
>
> # source and patch files
> SRC_URI="https://github.com/npat-efault/${NAME}/archive/refs/tags/${VERSION}.tar.gz"
> REQUIRES=""
You don't need this if it's empty
> BUILD_REQUIRES+="gcc-g++"
This can be written just '='
> MAKEOPTS=""
Does this do anything?
Otherwise, looks good. Thanks.
I added picocom to your packages.
next prev parent reply other threads:[~2023-01-07 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 23:02 Libor Ukropec
2023-01-07 13:26 ` Jon Turney [this message]
2023-01-07 17:03 ` Libor Ukropec
2023-01-07 17:58 ` Jon Turney
2023-01-07 18:59 ` Libor Ukropec
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=5d5a1cb9-0633-3eb8-7eea-5ab4b9c3f7eb@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=ace@seznam.cz \
--cc=cygwin-apps@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).