From: "Thomas Schmitt" <scdbackup@gmx.net>
To: grub-devel@gnu.org
Subject: Re: About the CLI of both grub-mkrescue versions
Date: Sun, 28 Sep 2014 20:28:42 +0200 [thread overview]
Message-ID: <12011546142310303634@scdbackup.webframe.org> (raw)
In-Reply-To: <18490546117595467817@scdbackup.webframe.org>
Hi,
how about this:
-----------------------------------------------------------------
The C program gets renamed to grub-mkiso.c. The binary gets
installed under two names: grub-mkiso and grub-mkrescue.
If started as "grub-mkiso" the program implements the change in
the CLI. I.e. "--" marks the start of xorriso -as mkisofs options.
If started as "grub-mkrescue", an own argument parser implements
the old behavior of the grub-mkrescue(.in) script. I.e. unknown
arguments are used as xorriso -as mkisofs options. The unknown
argument "--" then causes xorriso -as mkisofs emulation to end.
-----------------------------------------------------------------
This would avoid to bother scripting users of grub-mkrescue
or maintainers of things like
http://www.unix.com/man-page/linux/1/GRUB-MKRESCUE/
The name grub-mkiso would be well appropriate because the program
produces GRUB2 bootable ISO images not only for rescue systems,
but also for system distributions and live CDs.
Needed would be:
- Legacy parser in the C program compatible to old grub-mkrescue.in
- New help text in C program to reflect grub-mkiso CLI.
- Old help text in C program gets triggered by the legacy parser.
It should mention that there is also the more modern grub-mkiso.
- Update docs/grub.texi, describing grub-mkiso and mentioning that
grub-mkrescue is outdated.
Except the legacy parser, all these tasks have to be addressed
anyway, in order to reflect the current change from grub-mkrescue.in
to grub-mkrescue.c.
Have a nice day :)
Thomas
next prev parent reply other threads:[~2014-09-28 18:30 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 [this message]
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
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=12011546142310303634@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 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.