From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: RE: [ITP] aide 0.17.3
Date: Sat, 13 Nov 2021 20:37:11 -0500 [thread overview]
Message-ID: <03b901d7d8f8$258cea40$70a6bec0$@pdinc.us> (raw)
In-Reply-To: <fab0e4a0-5df1-0031-3fac-792cd8869475@SystematicSw.ab.ca>
> -----Original Message-----
> From: Brian Inglis
> Sent: Friday, November 12, 2021 11:50 AM
>
> On 2021-11-12 05:48, Jason Pyeron wrote:
> >> -----Original Message-----
> >> From: Brian Inglis
> >> Sent: Wednesday, November 10, 2021 11:25 AM
> >>
> >> On 2021-11-10 05:33, Jason Pyeron wrote:
> >>> On Sunday, October 31, 2021 10:37 AM, Jason Pyeron wrote:
> >>>> On Sunday, October 31, 2021 8:48 AM, Jon Turney wrote:
> >>>>> On 29/09/2021 15:27, Jason Pyeron wrote:
> >>>>>> On Friday, July 30, 2021 10:34 AM, Jason Pyeron wrote:
> >>>>>>> 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.
> > ...
> >>>>>> Upstream has expressed willingness to review/track patches, if
> >>>>>> needed.
> >>
> >> Good idea to submit patches upstream, as it reduces the number of
> >> patches you have to maintain and rebase, and they may have a better idea
> >> of how to achieve the same goal with more generality having their
> >> knowledge of the package source and build.
> >>
> > ...
> >>>> The attached (with required patch) has been in testing on multiple
> >>>> windows servers since late July. They can also be reviewed on
> >>>> github [2].
> >> Using github is an issue for some: gitlab, bitbucket, etc. may or may
> >> not be.
> >>
> >> That is why it is a good idea to checkout your repo on a playground
> >> branch, then force push your repo to:
> >>
> >> ssh://cygwin@cygwin.com/git/cygwin-packages/playground
> >>
> >> and post the jobs.cgi, run, and log links.
> >
> > Run 3524: https://cygwin.com/cgi-bin2/jobs.cgi?id=3524
> >
> > x86, x86_64 build logs: https://github.com/cygwin/scallywag/actions/runs/1453082339
>
> To suppress source patch generation at the end of source packaging:
>
> >>> Creating source patches
> include/util.h | 1 +
> 1 file changed, 1 insertion(+)
>
> need to add near the end of your definitions:
>
> DIFF_EXCLUDES=include/util.h
Not sure I understand this, that file is explicitly patched to build. See:
commit e4818534fa1165ba4dc066ff90b78d0885a61fac
Author: Jason Pyeron <jpyeron@pdinc.us>
Date: Tue Aug 3 11:10:17 2021 -0400
cygport file and patch to build Aide 0.17.3 on Cygwin
A aide-0.17.3-1.cygwin.patch
-Jason
next prev parent reply other threads:[~2021-11-14 1:37 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
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 [this message]
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='03b901d7d8f8$258cea40$70a6bec0$@pdinc.us' \
--to=jpyeron@pdinc.us \
--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).