public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: Question about packaging and cygport
Date: Fri, 28 Jun 2019 13:51:00 -0000	[thread overview]
Message-ID: <be104a10fa647832cb0445a46f59ed1c@smtp-cloud9.xs4all.net> (raw)
In-Reply-To: <CA+kUOak20hAjGbZDuOuMHHHjDDCoTuSbtOMjpBq72zw7e8WmTQ@mail.gmail.com>

On Fri, 28 Jun 2019 14:01:45, Adam Dinwoodie  wrote:
[snip]

> have uploaded to provide via the packaging distribution mirrors. Some
> maintainers will keep their cygport files on GitHub or similar (I do),
> but that's entirely down to the preferences of the individual
> maintainer, and I don't know where or even if the cmake-cygport
> files are available anywhere else.

?

Pick a Cygwin mirror

 - https://cygwin.com/mirrors.html

e.g. "Twente" and select cmake (the pkg we are talking about):

 - http://ftp.snt.utwente.nl/pub/software/cygwin/x86_64/release/cmake/

Look for the tarrballs that terminate w/ -src.tar.xz. If the package has
a .cygport file, you will find it in the source tarballs.

Henri


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

  parent reply	other threads:[~2019-06-28 13:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-28 10:56 Arjen Markus
2019-06-28 11:20 ` Andrey Repin
2019-06-28 13:02 ` Adam Dinwoodie
2019-06-28 13:13   ` Arjen Markus
2019-07-01 12:40     ` Marco Atzeri
2019-06-28 13:51   ` Houder [this message]
2019-06-28 14:01     ` Arjen Markus
2019-07-01 12:41       ` Marco Atzeri
2019-07-01 12:51         ` Arjen Markus
2019-07-08  4:23           ` Arjen Markus
2019-07-08  9:01             ` Arjen Markus
2019-07-08 12:36               ` Marco Atzeri
2019-07-08 13:04                 ` Arjen Markus
2019-07-08 18:32           ` Brian Inglis
2019-07-09  6:40             ` Arjen Markus

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=be104a10fa647832cb0445a46f59ed1c@smtp-cloud9.xs4all.net \
    --to=houder@xs4all.nl \
    --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).