From: marco atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Silver Zachara <silver.zachara@gmail.com>
Subject: Re: More cygwin installations
Date: Sun, 25 Sep 2016 16:58:00 -0000 [thread overview]
Message-ID: <CAB8Xom8bftVc8mDm9x1EQj70sDfvdqk=ABRxivosF_hXKRtn6A@mail.gmail.com> (raw)
In-Reply-To: <14910411119.20160925111705@yandex.ru>
On Sun, Sep 25, 2016 at 10:17 AM, Andrey Repin <anrdaemon@yandex.ru> wrote:
> Greetings, Silver Zachara!
>
>> can i install cygwin multiple times to different folders? E.g.
>> c:\cygwin64, c:\cygwin64_x_test1, c:\cygwin64_x_test2
>
>> I want to know, if there will not be any collisions or something similar.
>> Or there have to be only one cygwin installation?
>
> You MAY use multiple parallel installations. But it is least advisable for
> people unfamiliar with environment, clashes may occur and you would have a
> hard(-er) time figuring them out.
I don not see such big risk with multiple installations.
Basic rules appliy:
- separate PATH between the diffent installations.
defining CYGWIN_NOWINPATH help on it
- don't mix services as they will be called all in the same way by
the different installation.
> If you indeed need test installations, a virtual machine is the better route,
> IMO.
Usually if Virtual Machines are possible there are less motives to use cygwin;
people developing for cygwin are of course the exception.
> With best regards,
> Andrey Repin
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
prev parent reply other threads:[~2016-09-25 12:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 14:17 Silver Zachara
2016-09-24 22:40 ` Ken Brown
2016-09-25 10:57 ` Andrey Repin
2016-09-25 11:00 ` Silver Zachara
2016-09-25 16:58 ` marco atzeri [this message]
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='CAB8Xom8bftVc8mDm9x1EQj70sDfvdqk=ABRxivosF_hXKRtn6A@mail.gmail.com' \
--to=marco.atzeri@gmail.com \
--cc=cygwin@cygwin.com \
--cc=silver.zachara@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).