well how about just create symlinks to the new names.. that way things can go on as they are for now, and slowly as the packages are "enhanced" in future, they can be recreated with the new names, and the symlinks can be swaped to the old names..
or just do that, go with the newer naming scheme, and make symlinks for the old names.. just to smooooooth over the transition.. and the docs need not be changed instantly. but it is a pain, remembering the number of different names for different tools is a huge hassle. and the dumb use of caps and smalls doesn't help either why use MandrakeUpdate when the norm is to assume mandrakeupdate (I don't expect mixed case on system tools and I doubt many others do either. There are worse examples, how about InteractiveBastille if it wasn't for the tab key, I would never get that right on my own.. mandrake is supposed to be easier, why make it harder? how about truely usefull names. mdk-fonts mdk-menu mdk-firewall mdk-firewall-advanced mdk-config mdk-xsetup mdk-hardware I can tell what these do just by looking at them, can you say the same for their current naming scheme (assuming no prior knowledge of mandrake.) rgds Frank -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, 19 February 2002 11:26 PM To: [EMAIL PROTECTED] Subject: Re: [Cooker] RE: Suggestion: Mandrake Naming Layout Change "John Herdy" <[EMAIL PROTECTED]> writes: > The MDK<tool> naming convention sounds great. It makes our lives a lot easier. > Can someone from the Mandrake-team respond to this? As for me, the name switching is a much too big work. You have to change the names in tools, documentation and people-s-brain. The latter being very hard.
