On 7/31/2013 17:54, Linda Walsh wrote:
Warren Young wrote:
Just to emphasize: if both 32- and 64-bit Cygwin bin dirs are in your
PATH at the same time, you will get complaints in the terminal window
------
Ok, but would it be desirable (or wouldn't it be)
to have only 1 /etc, /var, /home? dir,
Sure. But what's stopping you from doing that today? Symlinks work
just fine across the /cygdrive boundary separating your Cygwins.
I keep very little in /home, mainly just dot files and symlinks into
/cygdrive/c/Users/mylogin. The actual data I keep under c:\Users. That
is, ~mylogin/Documents is a symlink to My Documents, etc. Similar for
Pictures, Downloads, AppData, ...
I have a bunch of scripts I've written in ~/bin, but those get checked
into a local Subversion repository, so I can keep those updated across
Cygwins easily enough. Ditto with compiled programs I've written: just
check out and rebuild on the other Cygwin when they change.
then maybe in your bashrc have
it do a cygmount or create a softlinke from /bin32 -> /bin or /bin64->/bin
(and same for lib)?
You can't just merge the two bin/lib dirs. The executable names
conflict. My solution involving a "cygwin2.dll" is the only solution I
see. And again, it's packed with potential pain.
I don't think it will turn out well to try to have people
maintain 2 sets of configuration files...
People have been inventing new ways to keep /etc synchronized for
decades. Most relevant to Cygwin today are symlinks, etckeeper,
Puppet/Chef/Cfengine, YourFavoriteVCS...
--
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
