23 May 2013 10:44
Global 32/64 bit collision issues
Hi guys, Yaakov brought this up in a private IRC conversation a couple of weeks ago, but I dismissed it at the time. But I guess we have to discuss this. Consider somebody has 32 and 64 bit Cygwin installed in parallel. At least for developers and package maintainers this won't be that uncommon. Now, they will run in parallel just fine, and most of our packages don't do anything outside of the cygwin installation dir. However, there are a couple of packages which change the system on a global basis. I see three groups here: 1. Packages installing shortcuts in the start menu and/or desktop (this includes setup itself). #1 types could be solved rather easily if we attach a "64" to all the created shortcuts. But do we really want that, considering a setup for a "normal" user with only a single installation? What are the trade-offs? 2. Packages installing services. #2 packages have a service name collision. Obviously you can't install two services called "cron". Should the package install its service under another name, again by just attaching a "64" to the service name? This would require to change the service installer scripts to check(Continue reading)
RSS Feed