From: Andrey Repin <anrdaemon@yandex.ru>
To: Nicholas Clark <nicholas.clark@gmail.com>, cygwin@cygwin.com
Subject: Re: cygwin@cygwin.com
Date: Mon, 03 Aug 2015 19:20:00 -0000 [thread overview]
Message-ID: <168268631.20150803221644@yandex.ru> (raw)
In-Reply-To: <CAKNeuBrRbQXfQJE7SGAAuK3s7ff-hcghu9tv39==O_ktJz33_w@mail.gmail.com>
Greetings, Nicholas Clark!
> I remember seeing a bunch of traffic on the subject of rebasing a few
> years ago, with people saying that it wouldn't be necessary once we
> moved over to 64-bit Cygwin. Did that wind up being true?
I see no reason to think otherwise. 64*bit address space is much leaner on the
subject.
However, the very process of rebasing the applications has nothing to do with
platform specs.
Apps are built on different machines, and their address space may collide,
when they meet on one target system.
64-bit platform just offer more space, meaning that more applications can be
installed that rely on POSIX address space semantics.
Still, you should only install what you are actually using.
> I've got some in-house tools that some of our developers want to use
> on Cygwin, and I've been thinking about the best way to maintain
> remote installations. If I use some kind of scripted
> deployment/update, do I actually need to keep everything rebased?
setup.exe offer all the tools you need for automatic installation.
--
With best regards,
Andrey Repin
Monday, August 3, 2015 22:12:38
Sorry for my terrible english...
--
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:[~2015-08-03 19:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 17:26 cygwin@cygwin.com Nicholas Clark
2015-08-03 19:20 ` Andrey Repin [this message]
2015-08-04 7:44 ` cygwin <at> cygwin.com Achim Gratz
-- strict thread matches above, loose matches on Subject: below --
2019-04-26 9:47 cygwin@cygwin.com kjur
2009-07-27 2:00 cygwin@cygwin.com leena21
2009-07-27 4:33 ` cygwin@cygwin.com Tim Prince
2001-12-04 3:09 cygwin@cygwin.com Thomas Schindler
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=168268631.20150803221644@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=nicholas.clark@gmail.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).