This is the mail archive of the
cygwin-apps
mailing list for the Cygwin project.
Re: Global 32/64 bit collision issues
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin-apps at cygwin dot com
- Date: Tue, 28 May 2013 12:26:27 +0200
- Subject: Re: Global 32/64 bit collision issues
- References: <20130523084435 dot GB13513 at calimero dot vinschen dot de> <51A2C50A dot 5090405 at users dot sourceforge dot net> <20130527100409 dot GD2483 at calimero dot vinschen dot de> <BLU173-W111D5EE8B1171370E465CEB5960 at phx dot gbl> <20130527143315 dot GA28463 at calimero dot vinschen dot de> <51A41821 dot 7050805 at gmx dot de>
- Reply-to: cygwin-apps at cygwin dot com
On May 28 04:36, Herbert Stocker wrote:
> But there is also a flaw:
>
> Imagine a user who has only a 32 bit installation.
> This algorithm would install the services without a '32' suffix.
> -> correct
> Then the user installs the 64 bit Cygwin, and now the scripts in the
> 32 bit Cygwin would try to access their services with the '32' suffix
> appended.
>
> Therefore some config setting that tells what to append seams
> necessary, be it an environment variable or a registry setting.
>
> If the user should not be bothered with such a setting at installation
> time, the 64 bit setup could rename all 32 bit services and short cuts
> to have the '32' suffixes.
You can't just rename services, that's kind of heavy-handed. This is
also a functionality which doesn't belong in setup, really. Also, how
does setup is supposed to know which Windows service is a Cygwin
service, a 32 bit service, and then, if it's a service being part of the
distro or created manually by the user?
> But users may need to adopt their self-made
> scripts. Therefore leaving this setting to the user, seams best for me.
Only distro services are supposed to do anything, *if* we decide to
do anything.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat