public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Keith Christian <keith1christian@gmail.com>,
	The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Sharing my packages for CYGWIN
Date: Sun, 4 Dec 2022 18:45:41 +0000	[thread overview]
Message-ID: <7655f2c0-dc1a-12ad-f3c6-0dd5fa9b61b1@dronecode.org.uk> (raw)
In-Reply-To: <CAFWoy7HptB5_6Q9N4N=Ry-aPwijRxnRpG8NJrtMpYN_dJFn61A@mail.gmail.com>

On 18/11/2022 14:32, Keith Christian wrote:
> Carlo,
> 
> Since you are successfully creating Cygwin packages, one thing that
> would be very helpful is a detailed set of instructions for cygport to
> create a Cygwin package from source.
> There are instructions posted on the Cygwin website and other info
> about cygport, but I have not found a comprehensive document that
> makes packaging nearly "mistake-proof" for uninitiated packagers.
> (Maybe I'm not looking in the right place.)

I know our documentation could be improved, but you seem to be asking 
for something which seems impossible.

Some pieces of software are complex and very hard to package, and even 
experienced packagers can make mistakes.

Can you perhaps explain more specifically where you get stuck in the 
process, and cannot find help?

> E.g., I want to create an up to date Ansible package for personal use,
> as the current version in Cygwin is 2.8.4, and it appears Ansible is
> up to at least 2.10.7, as that version is available in Debian
> Bullseye.

As [1] suggests, you should start by taking the existing package and 
updating the version number.

Hopefully it just works, but we cannot possibly anticipate all of the 
package-specific problems that might arise.

[1] https://cygwin.com/packaging-contributors-guide.html#adopt

  reply	other threads:[~2022-12-04 18:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 15:18 Carlo B.
2022-11-17 16:03 ` Ken Brown
2022-11-18 14:32   ` Keith Christian
2022-12-04 18:45     ` Jon Turney [this message]
2022-12-04 18:45 ` Jon Turney

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=7655f2c0-dc1a-12ad-f3c6-0dd5fa9b61b1@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cygwin@cygwin.com \
    --cc=keith1christian@gmail.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).