From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub-mkrescue problems in argp_parse
Date: Wed, 29 Apr 2015 16:05:04 +0200 [thread overview]
Message-ID: <5540E510.6040002@gmail.com> (raw)
In-Reply-To: <20651564086002247807@scdbackup.webframe.org>
[-- Attachment #1: Type: text/plain, Size: 2063 bytes --]
On 24.04.2015 18:31, Thomas Schmitt wrote:
> 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.
>
-v collision is fixed.
We need for compatibility:
-o
-?
-d
-k
--output
--rom-directory
--xorriso
--grub-glue-efi
--grub-render-label
--label-font
--label-color
--label-bgcolor
--product-name
--product-version
--sparc-boot
--arcs-boot
--modules
--install-modules
--themes
--fonts
--locales
--compress
--core-compress
--directory
--override-directory
--locale-directory
--themes-directory
--grub-mkimage
--pubkey
--verbose
Are any of those a problem? In future we can make a rule to add only
options starting with --. We can add a test to ensure this. Do we need
any other requirements to avoid clashes?
> 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 ?)
>
They're there. If you have data suggesting otherwise, please detail it
>
>> 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
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> .
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 213 bytes --]
next prev parent reply other threads:[~2015-04-29 14:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2037922098.114.1428942601173.JavaMail.open-xchange@ronja.mits.lan>
2015-04-13 17:06 ` grub-mkrescue problems in argp_parse Andrei Borzenkov
2015-04-13 17:16 ` Dietmar Maurer
2015-04-13 17:49 ` Andrei Borzenkov
2015-04-13 19:10 ` Thomas Schmitt
2015-04-14 7:23 ` Dietmar Maurer
2015-04-14 9:16 ` Thomas Schmitt
2015-04-14 9:58 ` Dietmar Maurer
2015-04-14 10:07 ` Dietmar Maurer
2015-04-14 10:34 ` Thomas Schmitt
2015-04-24 15:54 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-04-24 16:31 ` Thomas Schmitt
2015-04-29 14:05 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2015-04-29 16:42 ` Andrei Borzenkov
2015-04-29 16:57 ` Thomas Schmitt
2015-05-07 14:40 ` Vladimir 'φ-coder/phcoder' Serbinenko
2015-05-07 17:19 ` Andrei Borzenkov
2015-05-07 18:41 ` Thomas Schmitt
2015-05-07 18:19 ` Thomas Schmitt
2015-04-24 17:14 ` Andrei Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5540E510.6040002@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.