X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_20,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org X-IronPortListener: Outbound_SMTP From: "Buchbinder, Barry (NIH/NIAID) [E]" To: "cygwin AT cygwin DOT com" Date: Tue, 11 May 2010 08:59:11 -0400 Subject: RE: Cygwin visual brand Message-ID: <0105D5C1E0353146B1B222348B0411A208E108C143@NIHMLBX02.nih.gov> References: In-Reply-To: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Steven Collins sent the following at Monday, May 10, 2010 4:19 PM >On Mon, May 10, 2010 at 13:36, Klaus Grue <> wrote: >> In conclusion, I suggest a new term is invented such as the Cygwin >> Package Manager (CPM) or something like that. Then one could simply >> write Cygwin Package Manager under the Cygwin icon and then explain >> in the text that: >> The Cygwin Package Manager (cpm.exe) can install Cygwin and manage >> Cygwin packages. Among other, it can install, uninstall, upgrade, and >> downgrade individual packages. It can also install and upgrade the >> entire Cygwin system and keep the system up to date. >> By the way, it would by nice if CPM could also uninstall Cygwin. It >> sends the message that you are confident in your system if you make >> it easy for users to uninstall it. And it smells suspicious to >> provide software without an uninstaller. > >I would tend to agree with Klaus on this point. The "setup.exe" >name is too generic. If I'm examining my downloads directory with a >non-graphical tool (let's say something like "ls" :-) ) then it is not >obvious the setup.exe file is associated ith Cygwin. I'm not a fan of >"cpm.exe" for two reasons. > >1) CPM already has a history as an operating system so using that name >would have the potential for confusing the users as well as opening the >project to possible trademark/copyright infringement issues. > >2) When I'm doing an "ls" of the directory containing "cpm.exe" it is >only slightly more obvious than "setup.exe" what the application is. > >With modern file systems, command line completion, and GUI file managers >there is little reason to shorten the name down to its initials. >"CygwinPackageManager.exe" communicates clearly what the program is >without any further need of explanation. I agree that setup is to generic. Additionally, sometimes the security settings/antivirus might not allow one to either download or run something called setup. Personally, I like . See . And although I've never used a Linux package manager, my impression from comments on this list is that setup really doesn't have all the functions that many people would expect in a package manager like rpm or apt. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple