public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: [PATCH 1/4] setup.exe
Date: Wed, 13 Feb 2013 19:30:00 -0000	[thread overview]
Message-ID: <20130213193003.GA5287@ednor.casa.cgf.cx> (raw)
In-Reply-To: <87obfo58ta.fsf@Rainer.invalid>

On Wed, Feb 13, 2013 at 08:10:25PM +0100, Achim Gratz wrote:
>Christopher Faylor writes:
>> Regarding the autorebase changes, I am not against the idea of implementing
>> a general purpose mechanism to have setup.exe "do something" when it notices
>> certain file patterns being added or deleted.  This would move the current
>> 'autodep' functionality from the "upset" program which creates setup.ini into
>> setup.exe itself.
>
>I've had a brief look, I would not want to add another (regex) library
>to the sources, but if std::regex can be used (I haven't checked which
>version of gcc first had it), this should not be too difficult to
>implement.
>
>Another question is how to call this, I'd rather use "autorun" rather
>than "autodep" (but I haven't really made up my mind).  The semantics
>would roughly be that the package plus its dependencies must be
>installed and then whenever the autorun regex matches, a script that has
>been installed with the package is run.  Those scripts should not be in
>/etc/postinstall and for general use it would probably be useful to be
>able to chose if it gets run before or after the postinstall scripts.

The autodep/autorun wasn't an either/or.  We need the autodep and, while
you may need the ability to unconditionally run programs whenever
setup.exe is executed, the Cygwin project don't.  However, you could get
the behavior you want with autodep with something like:

autodep: .

cgf

  reply	other threads:[~2013-02-13 19:30 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 17:24 [PATCH] setup.exe Achim Gratz
2013-01-18 18:28 ` Ken Brown
2013-01-18 21:09 ` Christopher Faylor
2013-01-19  7:41   ` Achim Gratz
2013-01-19 17:18     ` Christopher Faylor
2013-01-19 20:47       ` Achim Gratz
2013-01-19 21:20         ` Christopher Faylor
2013-01-20  3:35           ` green fox
2013-01-20  6:53             ` Christopher Faylor
2013-01-21  7:03               ` green fox
2013-01-21  7:32                 ` Christopher Faylor
2013-01-21  9:46                   ` green fox
2013-01-21 16:01                     ` Christopher Faylor
2013-01-21 19:32                       ` green fox
2013-01-21 20:16                         ` Christopher Faylor
2013-01-20  7:16             ` Achim Gratz
2013-01-21  9:17               ` green fox
2013-01-20  7:23           ` Achim Gratz
2013-01-21 17:58             ` Achim Gratz
2013-01-25 22:07 ` [PATCH 0/4] setup.exe Achim Gratz
2013-01-25 22:10   ` [PATCH 1/4] setup.exe Achim Gratz
2013-02-01 14:40     ` Jon TURNEY
2013-02-01 15:11       ` marco atzeri
2013-02-01 17:10         ` Christopher Faylor
2013-02-01 16:08       ` Achim Gratz
2013-02-08 17:09     ` Jon TURNEY
2013-02-08 21:30       ` Achim Gratz
2013-02-10 19:23         ` Christopher Faylor
2013-02-11 19:40           ` Achim Gratz
2013-02-12 20:02           ` [PATCH 0/3] setup: implement CLI options Achim Gratz
2013-02-12 20:06             ` [PATCH 3/3] " Achim Gratz
2013-02-12 20:06             ` [PATCH 2/3] " Achim Gratz
2013-02-12 20:06             ` [PATCH 1/3] " Achim Gratz
2013-02-13 19:10           ` [PATCH 1/4] setup.exe Achim Gratz
2013-02-13 19:30             ` Christopher Faylor [this message]
2013-02-13 21:25               ` Achim Gratz
2013-02-13 22:08                 ` Christopher Faylor
2013-02-14 20:31                   ` Achim Gratz
2013-02-15  0:22                     ` Christopher Faylor
2013-02-15 19:52                       ` Achim Gratz
2013-02-16 18:39                         ` Christopher Faylor
2013-02-16 20:11                           ` Achim Gratz
2013-02-16 21:16                             ` Corinna Vinschen
2013-02-17 17:20                               ` Christopher Faylor
2013-02-17 17:43                                 ` Corinna Vinschen
2013-02-17 18:02                                   ` Christopher Faylor
2013-02-17 18:44                                     ` Achim Gratz
2013-02-17 19:21                                       ` Corinna Vinschen
2013-02-17 21:47                                         ` Christopher Faylor
2013-02-17 22:22                                           ` Christopher Faylor
2013-02-18 19:01                                             ` Achim Gratz
2013-01-25 22:11   ` [PATCH 2/4] setup.exe Achim Gratz
2013-01-25 22:11   ` [PATCH 0/4] setup.exe Achim Gratz
2013-02-01 15:05     ` Jon TURNEY
2013-02-01 16:48       ` Achim Gratz
2013-02-01 19:28       ` [PATCH 5/4] setup.exe Achim Gratz
2013-01-25 22:12   ` [PATCH 4/4] setup.exe Achim Gratz
2013-02-04 16:21   ` [PATCH 3/4] setup.exe 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=20130213193003.GA5287@ednor.casa.cgf.cx \
    --to=cgf-use-the-mailinglist-please@cygwin.com \
    --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).