From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] tractorgen 0.31.7
Date: Wed, 2 Jun 2021 11:43:39 -0600 [thread overview]
Message-ID: <05691e2d-f459-dc66-555e-0ea77e976bde@SystematicSw.ab.ca> (raw)
In-Reply-To: <cd51ca42-3f1b-aa27-92f8-61fceadea6df@cornell.edu>
On 2021-06-02 10:12, Ken Brown via Cygwin-apps wrote:
> On 6/1/2021 1:36 PM, Marco Atzeri via Cygwin-apps wrote:
>> On 01.06.2021 14:41, Daisuke Fujimura via Cygwin-apps wrote:
>>> Hello,
>>> [ITP] A new package proposal: tractorgen
>>> - tractorgen
>> The package seems not very used.
>> Not sure fit in our scope for missing the need for a vote
>> Opinion from the other maintainers ?
> Since the package doesn't appear to be in any of the standard Linux
> distributions, I think our policy is that it needs affirmative votes
> from 5 maintainers.
+1 It is packaged in BSD ports.
We need to offer more relaxation and fun, and I intend to explore the
games category more: I should do so while waiting for cygport builds; I
used to play GNU games a long time ago, while waiting for builds.
I installed Cygwin sl long ago, rescued {asr,funny}-manpages from Debian
when they announced dropping them, and have built those, cowsay, moo,
and others for local installs.
I have also saved archives of {comp,mod}.sources*, Heirloom, and Moby
collections, as many of those games/utilities originated there.
I have hesistated to ITP them: if there is interest in ASCII Art
games/utilities, I will offer those I have.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
prev parent reply other threads:[~2021-06-02 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 12:41 Daisuke Fujimura
2021-06-01 17:36 ` Marco Atzeri
2021-06-02 16:12 ` Ken Brown
2021-06-02 17:43 ` Brian Inglis [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=05691e2d-f459-dc66-555e-0ea77e976bde@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).