>?On Thu, Mar 06, 2008 at 04:07:00PM +0100, Paul-Kenji Cahier wrote: >>>?On Thu, Mar 06, 2008 at 12:43:41PM +0100, Peter Klavins wrote: >>>>1. Since my downloads directory may contain many files, amongst which >>>>other generic setup.exe's, could the cygwin setup program be changed to >>>>something more related to cygwin, e.g., cygsetup.exe? That would fit >>>>well with other cygwin bits like cyg*.dll and cyg*.exe. At the moment >>>>the only hint that it belongs to cygwin is its icon, which you only see >>>>if you're looking at it with Explorer.
>>>?No, we're not going to change the name of the program. It's been called >>>?setup.exe for many years and changing the name now would be guaranteed >>>?to generate confusion. >>I will have to agree that setup.exe is one of the most >>common filenames and it's very confusing to keep it that way. >>However obviously cygwin seems anchored in backward compatibility >>(which is not such a bad policy) so I doubt this is going to change. >?I mentioned why we are not going to change and Dave Korn provided much >?more detail. This is only "backwards compatibility" in the broadest >?sense. This is not a debate. It really is not going to change. Never implied it was going to change. I was being honest, and not trying to have anything changed. Sorry if it sounded like that. Plus this is something really fickle and unimportant, so there is no reason to be so rash about it. I will just have to disagree about the "general confusion" that renaming would supposedly cause, because that's total non-sense. It's not as if you're changing the default path of install, or suddenly changing something most people do care about. And if some do, they're either very special or simply cant adapt at all, in which case they should not weight in the decision. It's as if saying that if your soda bottle were to have a change of the position of the text on it, it'd suddenly become confusing.(and that's exactly what a filename is, a readable visual wrapping around data) There's nothing wrong about changing this or not changing this. It's just a matter of choice, which I think you've made clear. >>Peter Klavins: What you should do is rename it at download time. >>>?If mixing cygwin downloads with other downloads is causing you confusion >>>?then the obvious thing to do is to use another directory. >>Managing files without icons is not that uncommon. >>Confusion will of course arise in these cases. >?I have no idea what this means. Just create a shortcut to >?http://cygwin.com/setup.exe and put it on your desktop. Create a >?directory just for cygwin downloads. Click on the shortcut when you >?want to update and make sure that you set the download area to your >?newly created directory. I just meant that for people that move around with installers or use launchers/cli(automated bat files anyone?) it can get confusing when multiple files are called setup.exe. And obviously one can make a dedicated shortcut, rename the file and/or make a dedicated directory which is why there is, indeed, no compelling reason to change it. P-K. Cahier -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
