public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Cc: fergusd84@outlook.com
Subject: Re: grap, anybody?
Date: Tue, 07 Jan 2020 22:41:00 -0000	[thread overview]
Message-ID: <c5dd56f0-ce93-1378-78a4-92636cbc4b41@gmail.com> (raw)
In-Reply-To: <LNXP265MB143684B025EAFDE83FEF783AA43F0@LNXP265MB1436.GBRP265.PROD.OUTLOOK.COM>

Am 07.01.2020 um 23:10 schrieb Fergus Daly:
> 
> I'm just not up to it, but given the trivial nature of the single required patch, is there anybody out there who could take this on for the Cygwin provision?
> (There must be 00s of users who need it? I'm truly surprised that grap, or rather its lack, hasn't had a much higher historical profile in this forum.)
> Does it matter that the source files https://www.lunabase.org/~faber/Vault/software/grap/grap-1.45.tar.gz are "owned" by somebody else?
> (I imagine it does. Just asking.)
> 


1) This is not a forum, but a mailing list.

2) Where is the sorce file is irrilevant. The LICENSE matters,
   but as the package is in Debian I assume it is fine.

3) about making a package
   "Somebody Has To Do Itâ„¢. Are you volunteering? "
    https://cygwin.com/acronyms/#SHTDI


All maintainers are volounteers. They build packages that they care.
It seems grap has not passed the minimal threshold for anyone to
volounteer for it.
Feel free to offer yourself
https://cygwin.com/packaging-contributors-guide.html

Regards
Marco



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2020-01-07 22:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 17:36 Fergus Daly
2020-01-07 22:10 ` Fergus Daly
2020-01-07 22:41   ` Marco Atzeri [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-01-06 21:40 bonhard
2020-01-07  6:17 ` Brian Inglis
2020-01-07 11:28 ` Takashi Yano

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=c5dd56f0-ce93-1378-78a4-92636cbc4b41@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=fergusd84@outlook.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).