public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Arjen Markus <arjen.markus895@gmail.com>
To: Andrey Repin <cygwin@cygwin.com>
Subject: Re: Question about packaging and cygport
Date: Fri, 28 Jun 2019 13:13:00 -0000	[thread overview]
Message-ID: <CAMCbSMoYFYpv1a3MpD2HKUBBipAcVnTOvOST5G-oz-b-btDcjA@mail.gmail.com> (raw)
In-Reply-To: <CA+kUOak20hAjGbZDuOuMHHHjDDCoTuSbtOMjpBq72zw7e8WmTQ@mail.gmail.com>

Ah, thanks a lot - I will pass on this information to my
co-maintainer. I did find
https://github.com/tkelman/cygwin-cmake/blob/master/cmake.cygport but
I do not know what its status is or even if it has any ;).

Regards,

Arjen

Op vr 28 jun. 2019 om 15:02 schreef Adam Dinwoodie <adam@dinwoodie.org>:
>
> On Fri, 28 Jun 2019 at 11:56, Arjen Markus wrote:
> > In the context of the PLplot project (plplot.sf.net) we are interested
> > in the details of how software is packaged for Cygwin, in particular
> > how CMake is packaged (development of this package is rather fast and
> > we attempt to keep up with it, so that we can clean up the various
> > workarounds).
> >
> > To better understand the process, we would like to know, how packaging
> > is arranged - is that via "cygport" files? And if so, what is the
> > authorative location of these files (notably cmake.cygport)? If some
> > other method is used, could you enllighten us about the actual
> > process?
>
> Cygport provides a way for maintainers to build packages that are
> compatible with the Cygwin package distribution tools, so most
> maintainers use it, but I think there are still a few packages that
> are maintained without cygport; provided maintainers upload packages
> that are compatible with the package distribution tools used by the
> Cygwin project, maintainers are free to use whatever tools they like.
> In the specific case of cmake, that package does use cygport, but it's
> not guaranteed that all packages will.
>
> The only authoritative source of these files will be the source
> package downloads you can get through the Cygwin installer, by ticking
> the "Src?" box in the setup-(x86|x86_64).exe installer. Those are only
> guaranteed to include the source code itself, but for any package
> using cygport, you can expect they'll also include the cygport file
> and any associated files. There's no general repository for the
> packaging tools and configuration other than that which maintainers
> 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.
>
> Adam
>
> --
> 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
>

--
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:[~2019-06-28 13:13 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 [this message]
2019-07-01 12:40     ` Marco Atzeri
2019-06-28 13:51   ` Houder
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=CAMCbSMoYFYpv1a3MpD2HKUBBipAcVnTOvOST5G-oz-b-btDcjA@mail.gmail.com \
    --to=arjen.markus895@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).