public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] aide 0.17.3
Date: Sun, 31 Oct 2021 12:47:36 +0000	[thread overview]
Message-ID: <016f9850-f78d-dec7-412f-f74d6fb5b731@dronecode.org.uk> (raw)
In-Reply-To: <067001d7b53e$24465d70$6cd31850$@pdinc.us>

On 29/09/2021 15:27, Jason Pyeron wrote:
>> -----Original Message-----
>> From: Jason Pyeron
>> Sent: Friday, July 30, 2021 10:34 AM
>>
>> AIDE - Advanced Intrusion Detection Environment
>>
>> https://github.com/aide/aide/
>>
>> It is a GPL v2 tool for monitoring file system changes.
>>
>> There was no (mature?) Windows open source solution until AIDE was built and tested for
>> Cygwin. This fills a long standing gap in needs.
>>
>> Closed source alternative - Trip Wire.
>>
>> It is packaged and shipped with most Linux distributions - I am most familiar with the
>> RHEL packaging.
>>
>> I have built and tested the most recent stable and development versions.
>>
>> I will track the development versions for test package releases.
>>
>> Category Security.
>>
>> Thoughts?
> 
> There has been no response. It has been in test locally for 2 months now.
> 
> May I push the cygport to git and provide a test release?
> 
> Upstream has expressed willingness to review/track patches, if needed.
> 

Hi,

Thanks for offering to package and maintain this package, and apologies 
for the delay in responding.

Notwithstanding [1] (which needs updating), I look for 2 things in an ITP:

- a statement that the software uses an acceptable open-source license
- the cygport file (as an attachemnt or link) so it can be reviewed and 
tested

If you're still interested in progressing this, please provide the 
cygport file for discussion.

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

  parent reply	other threads:[~2021-10-31 12:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 14:34 Jason Pyeron
2021-09-29 14:27 ` Jason Pyeron
2021-09-30  0:07   ` Brian Inglis
2021-10-31 12:47   ` Jon Turney [this message]
2021-10-31 14:37     ` Jason Pyeron
2021-11-10 12:33       ` Jason Pyeron
2021-11-10 16:24         ` Brian Inglis
2021-11-12 12:48           ` Jason Pyeron
2021-11-12 16:49             ` Brian Inglis
2021-11-14  1:37               ` Jason Pyeron
2021-11-14  8:10                 ` ASSI
2021-11-14 14:39                   ` [PATCH} cygport src_fetch.cygpart PATCH_URI doc addition Brian Inglis
2021-11-14 12:49       ` [ITP] aide 0.17.3 Jon Turney
2021-11-14 16:36         ` Jason Pyeron
2021-11-14 17:00           ` Achim Gratz

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=016f9850-f78d-dec7-412f-f74d6fb5b731@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --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).