grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: About the CLI of both grub-mkrescue versions
Date: Sat, 29 Nov 2014 11:55:30 +0100	[thread overview]
Message-ID: <23046551324958644087@scdbackup.webframe.org> (raw)
In-Reply-To: <20141129083827.2832cebc@opensuse.site>

Hi,

Vladimir Serbinenko:
> I think that old parser is better. The only reason the change happened
> is that it's a bug that sneaked in during migration to C. It should be
> fixed.

Andrei Borzenkov:
> [...] Nor do I actually like "pass anything you
> do not understand" - it has potential to break if grub-mkrescue gets
> new options. 

I agree that it is a bug to make incompatible changes to the
grub-mkirescue CLI. But i also agree that this CLI is sub-optimal
in respect to future compatibility. It's just that i do not deem
sub-optimality a valid excuse for breaking interfaces.

Therefore my proposal to freeze grub-mkrescue CLI and to have
a new CLI with a new program name, while maintaining a common
backend for both CLI parsers.


> It is near to impossible to emulate old behavior using argp

What would be the advantage of using argp for the old CLI ?
The C version of the old CLI has the goal to be as compatible
as possible. It is straightforward to translate the shell code
of grub-mkrescue.in into equivalent C code.

-------------------------------------------------------------

Regardless which parser implementation gets chosen, there remains
the problem of the not yet implemented options from grub-mkrescue.in:

> >   printc (_("Not supported any more are:"));
> >   printc (_("        --modules , --grub-mkimage , --override-directory"));

Are their use cases obsolete ?
Shall their valid use cases be covered by other tools ?


Have a nice day :)

Thomas



      reply	other threads:[~2014-11-29 10:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  8:12 About the CLI of both grub-mkrescue versions Thomas Schmitt
2014-09-28 16:17 ` Andrei Borzenkov
2014-09-28 16:52   ` Thomas Schmitt
2014-09-28 18:28     ` Thomas Schmitt
2014-09-29  5:04       ` Andrei Borzenkov
2014-09-29  7:07         ` Thomas Schmitt
2014-10-01  7:25           ` Thomas Schmitt
2014-10-10 18:19             ` Andrei Borzenkov
2014-10-10 20:29               ` Thomas Schmitt
2014-11-28 19:41             ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-11-29  5:38               ` Andrei Borzenkov
2014-11-29 10:55                 ` Thomas Schmitt [this message]

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=23046551324958644087@scdbackup.webframe.org \
    --to=scdbackup@gmx.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).