public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Nick Nauwelaerts <nick.nauwelaerts@aquafin.be>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: [ITP] git-crypt 0.6.0
Date: Fri, 09 Aug 2019 04:17:00 -0000	[thread overview]
Message-ID: <b0378c30debe48b08a0688a2d941f8e2@aquafin.be> (raw)

heya,

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.

cygport file & patches are here: https://github.com/inphobia/git-crypt.cygport

cygport file was written by me, windows patches came from the issue tracker, a link to the original patch is included as a comment in each patch file.

it completes all cygport steps (compile, package, etc, ...) just fine and the resulting package seems to be compliant.

major distro references as requested for new packages:
https://software.opensuse.org/package/git-crypt
https://packages.debian.org/sid/git-crypt

license: gpl v3

tested on windows 10 x64 - 1903, cygwin 3.0.7




// nick

________________________________

Volg Aquafin op Facebook<https://www.facebook.com/AquafinNV> | Twitter<https://twitter.com/aquafinnv> | YouTube<http://www.youtube.com/channel/UCk_4P5BJ-MtEEDCkCsR_KqQ?feature=mhee> | LinkedIN<http://www.linkedin.com/company/aquafin/products> | Instagram<https://www.instagram.com/aquafin_nv/>

In het kader van de uitoefening van onze taken verzamelen we bij Aquafin persoonsgegevens. Hoe we omgaan met deze gegevens en wat de rechten van de betrokkenen zijn, kan je nalezen in onze privacy policy<https://www.aquafin.be/nl-be/privacy-policy>.

  P Denk aan het milieu. Druk deze mail niet onnodig af.

             reply	other threads:[~2019-08-09  4:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09  4:17 Nick Nauwelaerts [this message]
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
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=b0378c30debe48b08a0688a2d941f8e2@aquafin.be \
    --to=nick.nauwelaerts@aquafin.be \
    --cc=cygwin-apps@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).