public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Chad Dougherty <crd@acm.org>
To: Jon Turney <jon.turney@dronecode.org.uk>,
	"cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] minisign 0.10
Date: Sun, 9 Oct 2022 11:09:45 -0400	[thread overview]
Message-ID: <0d704fae-2f1b-d291-43d5-df44f414be2d@acm.org> (raw)
In-Reply-To: <e91eea1a-5183-f690-d542-8f1c443ea3ce@dronecode.org.uk>

On 2022-10-09 10:33, Jon Turney wrote:
> Thanks.
> 
> I think I'd like to be using minisign to sign setup.ini for Cygwin's 
> setup, rather than the accident waiting to happen which is libgpg, but 
> that's a whole other project...
> 

I admit that was an ulterior motive but I also recognize there's a whole 
lot more to it :)

I've used minisign to verify a few other things and I thought it would 
be another good exercise for me to get my feet wet on the packaging process.

> Comments I made about rsync.cygport on REQUIRES and src_compile() also 
> apply here.
> 

Ah, I think I understand better now.  I'll address the rsync update soon.

In the case of minisign, it uses CMake and needed to invoke cygcmake, 
that's why I left src_compile() there.  Is that wrong?  It didn't 
compile with that commented out even though I inherit cmake.

>> src_install() {
>>   cd ${B}
>>   cyginstall
>> }
> 
> I think this is the same as the default src_install, so can be omitted?
> 

Yep.

-- 
     -Chad


  reply	other threads:[~2022-10-09 15:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 13:52 Chad Dougherty
2022-10-09 14:33 ` Jon Turney
2022-10-09 15:09   ` Chad Dougherty [this message]
2022-10-09 16:05     ` Chad Dougherty
2022-10-10 13:42       ` 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=0d704fae-2f1b-d291-43d5-df44f414be2d@acm.org \
    --to=crd@acm.org \
    --cc=cygwin-apps@cygwin.com \
    --cc=jon.turney@dronecode.org.uk \
    /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).