Guten Tag Kristis Makris, am Donnerstag, 13. Dezember 2007 um 17:29 schrieben Sie:
> Who ever said that programs should be installed in "Program Files" ? Is > that a public standard ? Under Windows it is a standard to save programs in that path which lies behind %PRogramFiles%, this is C:\Program Files, C:\Programme or whatever. This is environment variables are made for and this is specified all over the MSDN. > The problem is that Windows *USERS* assume programs must always be > installed in a fixed path that Windows decided to change all of the > sudden. This is nonsense, of course one can install the files where ever he likes but the platform Windows has some specifications, though, which define common guidlines. Just like any other platform. > Programs don't need to always be installed in a fixed path. They can be > installed in C:\Perl, C:\Temp, D:\Windows\System, etc. If Windows was so > picky, and formal to want to have all its files installed in the same > path, a path it would NOT change between releases, then it would have > NOT used drive letters, but fixed paths. e.g. /usr/bin, like most of the > universe. That would have made sense. Oh no. Can't do that. This is nonsense, /usr/bin is nothing better than C:\Program Files. I know a lot of people who install all of their software in /usr/local in a standard Windows-way, saying everything regarding a program in one folder. Theres nothing fixed in /usr/bin, it's recommended to do it one way, not forbidden the other way around. That's exactly the same with Windows and has nothing to do with drive letters. If you want to mount your partition with drive letter D:, your're welcome, else just mount it in C:\SomePartition\OnSomeHDD\Somewhere or something very different. This kind of discussion is pretty useless. Installing your software according some common guidlines is just always a good idea because for example in Windows you have pre configured ACLs for the path behind %ProgramFiles% which differs from those directly used for the root on C: or any other drive letter. > I will not spend time releasing a Windows version that contains in > its .zip file all Scmbug files intented for "Program Files" and another > 64-bit Windows version that contains in its .zip file all Scmbug files > intented for installation in "Program Files (x86)". Nobody wants that, if you want to let the user decide, which is a pretty good idea in my oppinion, just get that absolute path out of the zip and no problem for anyone. > I will not also > release a version that does not list the Scmbug files under "Program > Files" *or something close to it* just to confuse users and have them > asking where they must move files. "Program Files" it is, and is not > changing. Now you define some guidelines for deploying software under Windows, guidelines, you just told to be crap some minutes ago. ;-) An absolute path in the zip file is just a bad idea regarding support because there are localized and different versions of Windows out there where this absolute path does harm. You don't need that absolute path, you just need a consistent, pre-defined directory structure for your installation and a little advice where the "SCMBug"-directory should be saved. Else you have the problem of Windows installations in german, where C:\Program Files is actually C:\Programme, the differences between x86 and x86-64 versions, the installation which doesn't even contain a drive letter C which is valid for the target installation of SCMBug and so on. The current zip is optimized for one thing: Your english x86 Windows, not for common support. At my company we provide software for the german justice which is one directory containing every software needed in a subversion repository. If one wnats to use it, just checkout and save anywhere, mst people will save it where you as the maintainer suggest it and the few not doing so will know where they saved it. As long as the directory structure is consistent, that's pretty uninteresting. > Even if the .bat files use %ProgramFiles%, the contents of the .zip file > cannot be dynamically moved (and don't even suggest that). That's what installers are made for, agreed. A simple zip is a pretty fine thing, just topped by direct checkout with Subversion. > If anything, I am only inclined to change the Windows version to install > in C:\Scmbug to better outline this Windows problem. There's no windows problem, one just shouldn't save absolute paths in a zip used to deploy software. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: [EMAIL PROTECTED] Web: http://www.am-soft.de AM-SoFT Potsdam GmbH, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 12480, Geschäftsführer Andreas Muchow _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
