From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>,
Nick Nauwelaerts <nick.nauwelaerts@aquafin.be>
Subject: Re: [ITP] git-crypt 0.6.0
Date: Sun, 01 Dec 2019 15:06:00 -0000 [thread overview]
Message-ID: <e698b6e7-3fec-397d-751a-b7562954dd63@dronecode.org.uk> (raw)
In-Reply-To: <6b6c1325b09f4fbeaf9d40fa3282d9be@aquafin.be>
On 10/08/2019 02:48, Nick Nauwelaerts wrote:
>> -----Original Message-----
>> From: cygwin-apps-owner@cygwin.com [mailto:cygwin-apps-
>> owner@cygwin.com] On Behalf Of Brian Inglis
>> Sent: Friday, August 9, 2019 08:15
>> To: cygwin-apps@cygwin.com
>> Subject: Re: [ITP] git-crypt 0.6.0
>>
>> On 2019-08-08 22:17, Nick Nauwelaerts wrote:
>>> git-crypt is a git plugin that transparently handles encryption/decryption
>>> of files in combination with git. i've used it on and off again when i need
>>> to place sensitive info on a location that could be public (or as most ppl
>>> seem to use it: to save dotfiles on github without all your private stuff
>>> being world readable). i've been using it sporadicly in cygwin for 2 months
>>> as well without any issues.
>>>
>>> as such i made a cygport of it, but i'm not quite clear on how the process
>>> works to submit it.
Thanks. Sorry for the delay in getting to this.
Some minor comments on the cygport file:
> # runtime deps to go in setup.hint, and note the escaped newline
> REQUIRES="git openssl"
The part of the comment about escaped newline doesn't make a lot of sense.
Are you sure that 'openssl' is required at runtime (and not just
libssl1.1, which is autodetected as a dependency)?
> # We use the src_compile and src_test provided by meson.cygclass
This comment is confusing since it's built with make?
> i figured if i made the cygport file and patches available you would
> import them in a build system like suse's openbuild to verify that no
> shortcuts were taken or my system was otherwise not comparable to
> normal install. come to think of it, kinda like what is proposed
> here: https://cygwin.com/ml/cygwin-apps/2019-08/msg00012.html :)
Unfortunately, we do not (yet) have a system to build packages from
those repositories.
> since i didn't bother with requesting access upload ofcourse fails,
> also making announce irrelevant. i'll will send an email with a key
> in the requested mail format asap.
I don't see an email with a key from you. If you are still interested
in progressing this, please provide a ssh key as per
https://cygwin.com/package-upload.html
next prev parent reply other threads:[~2019-12-01 15:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 4:17 Nick Nauwelaerts
2019-08-09 6:14 ` Brian Inglis
2019-08-10 1:48 ` Nick Nauwelaerts
2019-08-10 22:40 ` Brian Inglis
2019-12-01 15:06 ` Jon Turney [this message]
2019-12-05 19:59 ` Nick Nauwelaerts
2019-12-21 11:37 ` Marco Atzeri
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=e698b6e7-3fec-397d-751a-b7562954dd63@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-apps@cygwin.com \
--cc=nick.nauwelaerts@aquafin.be \
/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).