From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Does Cygwin setup modify dlls?
Date: Fri, 22 Sep 2017 16:49:00 -0000 [thread overview]
Message-ID: <612ef9c4-b110-bc1e-14a1-8ffe8d5e696d@gmail.com> (raw)
In-Reply-To: <trinity-9f7a208b-fc42-412d-9d36-4759c04d30a7-1506094306877@3c-app-gmx-bs22>
On 22/09/2017 17:31, Joachim Eibl wrote:
> Thank you for your answers.
>
>> This activity is performed by the script
>> /etc/postinstall/0p_000_autorebase.dash
>
> Is there a possibility to avoid the rebasing, e.g. for certain folders?
> In my case the intention was to use the Cygwin installer only, but the files in the package are not dependent on cygwin libraries. So forking is not an issue.
>
> Best regards,
> Joachim
>
setup does not perform rebase.
It is a post installation phase, performed by a special
package.
$ cygcheck -l _autorebase
/etc/postinstall/0p_000_autorebase.dash
/etc/preremove/_autorebase.sh
/usr/bin/rebase-trigger
/usr/bin/rebaselst
/usr/share/doc/Cygwin/_autorebase.README
If you are not installing on the cygwin tree I see no issue.
Otherwise you can consider to patch the "_autorebase" package
to exclude some files/trees
Regards
Marco
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-09-22 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 14:00 Joachim Eibl
2017-09-22 14:11 ` Eliot Moss
2017-09-22 14:46 ` Marco Atzeri
[not found] ` <trinity-4204847c-6bba-4606-b43c-8b376b96a945-1506094235587@3c-app-gmx-bs22>
2017-09-22 15:31 ` Joachim Eibl
2017-09-22 16:49 ` Marco Atzeri [this message]
2017-09-27 4:50 ` Andrey Repin
2017-09-27 10:04 ` Joachim Eibl
2017-09-22 15:49 ` Eliot Moss
2017-09-23 19:53 ` 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=612ef9c4-b110-bc1e-14a1-8ffe8d5e696d@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).