From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1YlgW2-00027A-U8 for mharc-grub-devel@gnu.org; Fri, 24 Apr 2015 12:31:46 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54454) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlgW0-00021p-Aj for grub-devel@gnu.org; Fri, 24 Apr 2015 12:31:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YlgVx-0001Tw-1F for grub-devel@gnu.org; Fri, 24 Apr 2015 12:31:44 -0400 Received: from mout.gmx.net ([212.227.15.18]:61992) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YlgVw-0001TZ-O0 for grub-devel@gnu.org; Fri, 24 Apr 2015 12:31:40 -0400 Received: from scdbackup.webframe.org ([79.192.89.235]) by mail.gmx.com (mrgmx003) with ESMTPSA (Nemesis) id 0MLujU-1YgBny3gZI-007jKl for ; Fri, 24 Apr 2015 18:31:39 +0200 Date: Fri, 24 Apr 2015 18:31:10 +0200 From: "Thomas Schmitt" To: grub-devel@gnu.org Subject: Re: grub-mkrescue problems in argp_parse Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit References: <553A6734.1030606@gmail.com> In-Reply-To: <553A6734.1030606@gmail.com> Message-Id: <20651564086002247807@scdbackup.webframe.org> X-Provags-ID: V03:K0:rJBZMy6QCX/gIWJmgJMRnl96DRyJzlb6qVy3XERKmCrVo+XYK25 290jRHErarVuDkXFsOseJMT6aWd/qsW8RD+dxNCp5IUvBMMJHFkzlZdBtW5IaFWAHSs5hRf pjErZFBBNjbyFXk+q70ZyeKfisuPmEiDUg0Db2rzOgz9nxb5GwaTaWxTGsk8oqklw03SQJb hSOVLc9rAAG5hlnVHaOEg== X-UI-Out-Filterresults: notjunk:1; X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 212.227.15.18 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Apr 2015 16:31:45 -0000 Hi, Vladimir wrote: > In all I kinda like > that grub-mkrescue would be drop-in replacement for xorrisofs/mkisofs > with additional boot semantics. Unfortunately it requires additional > discipline of avoiding option clashes like this one. You would have to reserve option names within xorriso's command set and its -as mkisofs option set. I would then avoid to give them a meaning in those sets. You would also have to resolve the old collision -v. There are further incompatibilities between old and new grub-mkrescue by the not yet implemented old options --modules --grub-mkimage --override-directory Will they be re-introduced ? (Should they ? What did they do ?) > In principle I'm ok with having more elegant command line if the name of > tool changes. Please count 1 vote for "grub-mkiso". :)) As said, both personalities could share one body to avoid duplication of maintainance effort. I propose to describe the new CLI in the docs as "unambiguous" rather than as "more elegant". Have a nice day :) Thomas