public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] asr-manpages, funny-manpages
Date: Sun, 8 May 2022 17:15:33 +0200	[thread overview]
Message-ID: <b9940d6f-d9e4-33e3-56b2-706f377eacff@seznam.cz> (raw)
In-Reply-To: <b378b6ed-4edf-a4df-01f2-593e9a8d4576@SystematicSw.ab.ca>

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

BTW, I noted LICENSE, CYGWIN_MAINTAINER, UPSTREAM_MAINTAINER variables 
... are they used/shown somewhere and is it a best practise to have them 
in the cygport script?

Regards,
Libor
> asr-manpages    20000406    alt.sysadmin.recovery manual pages
> 
> A set of humorous manual pages developed on alt.sysadmin.recovery
> (don't treat them seriously!). Some may be considered non-PC, NSFW, or
> offensive. The authors recommend these man pages be installed on every
> system.
> 
> Home    http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/misc/asr-manpages
> Arch    https://aur.archlinux.org/packages/asr-manpages
> DragonFly 
> https://github.com/DragonFlyBSD/DPorts/tree/master/misc/asr-manpages
> FreeBSD    https://www.freshports.org/misc/asr-manpages
> NetBSD    http://pkgsrc.se/misc/asr-manpages
> Gentoo    https://packages.gentoo.org/packages/games-misc/asr-manpages
> Slack    https://slackbuilds.org/repository/15.0/misc/asr-manpages/
> Ubuntu    https://launchpad.net/ubuntu/+source/asr-manpages
> Repology    https://repology.org/project/asr-manpages
> 
> https://drive.google.com/drive/folders/1b8DTVX_aiaZk90Lwd21W1kJ5NGOs73HX
> 
> funny-manpages    2.3    humorous manual pages
> A set of miscellaneous humorous manual pages (don't treat
> them seriously!). Some may be considered non-PC, NSFW, or offensive.
> You've been warned.
> 
> Home    https://github.com/ltworf/funny-manpages
> Arch    https://aur.archlinux.org/packages/funny-manpages
> Debian    https://packages.debian.org/sid/source/funny-manpages
> Gentoo    https://packages.gentoo.org/packages/games-misc/funny-manpages
> OpenSuSE    http://packman.links2linux.org/package/funny-manpages
> Slack    https://slackbuilds.org/repository/15.0/misc/funny-manpages/
> Ubuntu    https://launchpad.net/ubuntu/+source/funny-manpages
> Repology    https://repology.org/project/funny-manpages
> 
> https://drive.google.com/drive/folders/1n_P6qCF7LiOqMKsDpFz9qZsdvT4-BXd8
> 


  reply	other threads:[~2022-05-08 15:15 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 [this message]
2022-05-08 17:49   ` Brian Inglis
2022-05-14 13:15     ` Jon Turney
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:
  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=b9940d6f-d9e4-33e3-56b2-706f377eacff@seznam.cz \
    --to=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).