From: metaed@newjersey.metaed.com
To: cygwin-apps@cygwin.com
Subject: how to contribute a noarch utility without porting Icon, Noweb, and Cygport
Date: Wed, 3 May 2023 20:50:51 +0000 [thread overview]
Message-ID: <ZFLJK/elWRPrVp4n@newjersey.metaed.com> (raw)
I want to contribute a Cygwin port of my utility program "dtt". It is an
architecture-independent executable written in Perl 5 plus a man page. It comes
with supplementary docs in /usr/share/doc, including the complete source.
The package is built from source using the Noweb litprog tool, which also
requires the Icon programming language. Porting these to Cygwin could be a huge
undertaking. It would be much simpler for me to cross-compile, for lack of a
better term, where those tools are ported already -- namely, Slackware.
Instead of porting Cygport to Slackware, again it would be much simpler for me
to create the "binary" tarball and .hint file, a la
<https://www.cygwin.com/packaging-package-files.html>, and upload manually to
the noarch tree, a la <https://www.cygwin.com/package-upload.html>.
Is this an objectionable approach?
Cheers!
Edward
next reply other threads:[~2023-05-03 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 20:50 metaed [this message]
2023-05-03 21:06 metaed
2023-05-04 3:17 ` Brian Inglis
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=ZFLJK/elWRPrVp4n@newjersey.metaed.com \
--to=metaed@newjersey.metaed.com \
--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).