From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LvIlY-0000Md-Mp for qemu-devel@nongnu.org; Sat, 18 Apr 2009 18:12:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LvIlV-0000I7-2M for qemu-devel@nongnu.org; Sat, 18 Apr 2009 18:12:04 -0400 Received: from [199.232.76.173] (port=37235 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LvIlU-0000Hd-N0 for qemu-devel@nongnu.org; Sat, 18 Apr 2009 18:12:00 -0400 Received: from mail-gx0-f176.google.com ([209.85.217.176]:36238) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LvIlU-000387-8l for qemu-devel@nongnu.org; Sat, 18 Apr 2009 18:12:00 -0400 Received: by gxk24 with SMTP id 24so2962604gxk.10 for ; Sat, 18 Apr 2009 15:11:58 -0700 (PDT) Message-ID: <49EA5025.9010108@codemonkey.ws> Date: Sat, 18 Apr 2009 17:11:49 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [RFC][PATCH] Rename qemu into qemu-system-i386 and install a compat symlink References: <20090418160104.GA18120@volta.aurel32.net> <390D1A11-602E-4449-BEA0-EA431F91D109@web.de> <20090418174555.GA16360@hall.aurel32.net> <49EA1A15.1080803@mail.berlios.de> <20090418211222.GD16360@hall.aurel32.net> In-Reply-To: <20090418211222.GD16360@hall.aurel32.net> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Aurelien Jarno wrote: > On Sat, Apr 18, 2009 at 08:21:09PM +0200, Stefan Weil wrote: > >> Aurelien Jarno schrieb: >> >>> On Sat, Apr 18, 2009 at 07:22:20PM +0200, Andreas Färber wrote: >>> >>> >>>> Am 18.04.2009 um 18:01 schrieb Aurelien Jarno: >>>> >>>> >>>> >>>>> For historical reasons, qemu system on i386 is called qemu instead of >>>>> qemu-system-i386. This seems to confuse users. >>>>> >>>>> This patch installs it as qemu-system-i386, and create a compatibility >>>>> symlink qemu -> qemu-system-i386 as some tools may call it that way. >>>>> We can change or remove this symlink after a few releases when all the >>>>> tools have migrated to this new name. >>>>> >>>>> Signed-off-by: Aurelien Jarno >>>>> >>>>> >>>> In general a good idea imo, but don't just assume you can create >>>> symlinks on a given file system. Git uses hardlinks and copying as >>>> fallbacks iirc. >>>> >>>> >>> For hardlinks that's clear. For symlinks, what (file)systems are you >>> thinking of? >>> >> NTFS? >> > > Can someone tries what ln does on such a system? We may do a copy > instead in that case. > Windows has a concept of shortcuts (.lnk files). Cygwin's ln creates a shortcut to simulate a symbolic link. MSYS implements 'ln -s' by doing a file copy. I don't think it works for directories. I'm not personally opposed to just getting rid of 'qemu' for the 0.11 release. Sure, there will be some management tools that look for 'qemu' instead of 'qemu-system-i386' but I doubt they'll change things until the symlink goes away. We can issue a big fat ANNOUNCE to the mailing list that for 0.11 the executable name will change. Since it won't be for a few months, that should give people time to adjust. Regards, Anthony Liguori