From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Relationship between Cygwin and Cygwin Ports
Date: Mon, 08 Oct 2012 05:24:00 -0000 [thread overview]
Message-ID: <50726372.4060209@gmail.com> (raw)
In-Reply-To: <50720389.8060208@tiscali.co.uk>
On 10/8/2012 12:34 AM, David Stacey wrote:
>
> Hi.
>
> Earlier this evening I submitted an ITP for yasm. I didn't realise at
> that point that yasm was available in Cygwin Ports - which means that I
> have probably just trodden on Yaakov's toes, and for that I apologise.
>
> Please could someone kindly explain the difference between Cygwin and
> Cygwin Ports. Why are they kept separate, and under what circumstances
> could a package migrate between the two? Apologies if I should know
> this, but there doesn't appear to be mention of it in the Cygwin FAQ.
>
> Many thanks in advance for clarifying this,
>
> Dave.
>
Hi Dave,
Cygwin Ports is the personal effort of one of main Cygwin
package maintainers to provide additional packages.
He usually provide/test new version not ready or with additional
requirement than packages available in Cygwin, but also a lot of other
packages in addition at his mainstream effort:
http://cygwin.com/cygwin-pkg-maint
No problem to migrate a package assuming someone takes ownership
of the package in Cygwin as maintainer.
I took several of Yaakov's packages and adopted mainstream in the past,
usually checking/reusing what Yaakov already did.
No need to cancel your ITP.
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
next prev parent reply other threads:[~2012-10-08 5:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 22:34 David Stacey
2012-10-08 5:24 ` marco atzeri [this message]
2012-10-08 6:11 ` SPC
2012-10-11 2:35 ` Yaakov (Cygwin/X)
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=50726372.4060209@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).