public inbox for
 help / color / mirror / Atom feed
From: Jon Turney <>
To: "" <>
Subject: Re: [ITP] asr-manpages, funny-manpages
Date: Sat, 14 May 2022 14:15:57 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 08/05/2022 18:49, Brian Inglis wrote:
> On 2022-05-08 09:15, Libor Ukropec wrote:
>> Dne 07.05.2022 v 20:52 Brian Inglis napsal(a):
>>> I would like to offer to package the following projects for Cygwin.
>>> They have been extensively tested on my own system for decades. ;^>
>>> They are offered on the major distros listed below, and the cygport 
>>> builds are available in my Google Drive folders.
>> I haven't known them until now. Quite fun :)
>> Built and installed without any issue.
>> If I can give the GTG, here it is..
> Thanks - now I just need another four or so.
>> ... are they used/shown somewhere and is it a best practise to have 
>> them in the cygport script?
> Something I think should be documented somewhere, are tracked in some 
> other distros package trackers, easier to add on adoption, and useful 
> when you want to submit bug reports upstream.
> Defining then as shell vars mean you can use them for searching or in 
> commands.

'LICENSE' probably should be required by cygport, containing a SPDX ID 
or license expression.

I'm not sure about 'CYGWIN_MAINTAINER', since we already track that 
information elsewhere.

  reply	other threads:[~2022-05-14 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-07 18:52 Brian Inglis
2022-05-08 15:15 ` Libor Ukropec
2022-05-08 17:49   ` Brian Inglis
2022-05-14 13:15     ` Jon Turney [this message]
2022-06-04 13:02       ` LICENSE (was Re: [ITP] asr-manpages, funny-manpages) Jon Turney
2022-06-04 16:20         ` Brian Inglis
2022-05-14 13:09 ` [ITP] asr-manpages, funny-manpages Jon Turney
2022-05-14 18:24   ` Brian Inglis
  -- strict thread matches above, loose matches on Subject: below --
2021-04-11 17:48 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).