On Wed, Apr 2, 2008 at 2:48 PM, Bill Hoffman <[EMAIL PROTECTED]> wrote: > David C Thompson wrote: > > > > > > > I still like having a version numbered folder for CMake. > > > It would be: > > > > > > /Applications/CMake 2.6.0/CMake.app > > > /Applications/CMake 2.6.1/CMake.app > > > > > I don't want to beat a horse that's already down for the count, but I'm > > curious why having an executable with the version number in its name > > (e.g., /Applications/CMake 2.6.app ) is a bad idea; having folders > > in /Applications is un-Mac-like, especially when there will only be a > > > But, I do see commercial applications like quicken using the same strategy. > > > > > single thing inside the folder. Furthermore, if an application bundle is > > set up properly, it will still work should the user rename the folder -- > > for instance changing /Applications/CMake.app > > to /Applications/CMake-old.app should be OK. If CMake supports renaming > > the application bundle then you could even distribute it > > as /Applications/CMake.app and let users rename if they want multiple > > installed versions. Is CMake just not there yet? > > > > > > If you rename it, then the symlinks for the command line will be no good > anymore, other than that it works just fine with a rename. > > -Bill > >
Bill, Not having looked at the new CMake.app, if I do rename the .app bundle, is there a command in the CMake.app where I can re-establish the symlinks? If not, there probably should be. Both BBEdit and TextMate have this as a command under the "Help" menus. They also allow the choice of a few different locations such as /usr/local/bin or /usr/bin. I have seen lots of folders get created in /Applications: MS Office. Adobe Photoshop Adobe Illustrator Adobe Anything Really Applescript Missing Sync For Palm OS Roxio Toast Titanium Retrospect 6.0 Having folders in /Applications has precedence. Having version numbers in the folder name even has precedence. If everything can be contained in just the CMake.app bundle then there really isn't a need for an enclosing folder, especially if I can rename the .app and then re-establish the symlinks from within CMake.app itself. The folder didn't bother me as much as the all lower case name did. ;-) Just for an example, I have to keep both FireFox 1.5 and 2.x around, so I have folders for each inside /Applications. <philosophical note> Having a simple drag and drop CMake.app install is the most preferential because it looks like there isn't a need for an installer at this point as long as everything is contained in the CMake.app bundle. Just my 2 cents. -- Mike Jackson imikejackson _at_ gee-mail dot com _______________________________________________ CMake mailing list [email protected] http://www.cmake.org/mailman/listinfo/cmake
