From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] fs/iso9660: bugfix for iso9660/isofs.sh
Date: Thu, 1 Apr 2021 13:15:00 +0200 [thread overview]
Message-ID: <YGWrNBxxmVUgT72/@pevik> (raw)
In-Reply-To: <20210326014137.15718-1-zhanglianjie@uniontech.com>
Hi,
> Debian uses genisoimage to replace mkisofs, the prompt of genisoimage
> is the same as that of mkisofs.
...
> +++ b/testcases/kernel/fs/iso9660/isofs.sh
> @@ -12,6 +12,12 @@
> TST_NEEDS_CMDS="mkisofs"
> TST_NEEDS_TMPDIR=1
> TST_TESTFUNC=do_test
> +which mkisofs >/dev/null 2>&1
> +if [ $? -ne 0 ]; then
> + TST_NEEDS_CMDS="genisoimage"
> +fi
You can omit whole $? check:
if ! which mkisofs >/dev/null 2>&1; then
TST_NEEDS_CMDS="genisoimage"
fi
Also IMHO mkisofs is not dead [1], it just moved to schilytools [2] and some
distros use it (at least openSUSE [3]).
Thus asking for genisoimage (from cdrkit) can be a bit misleading.
But, is it really needed? Both Debian [4] and Fedora [5] creates
mkisofs symlink to genisoimage, Debian installs automatically genisoimage when
installing mkisofs.
Kind regards,
Petr
[1] https://wiki.osdev.org/Mkisofs
[2] http://sf.net/projects/schilytools/files/
[3] https://build.opensuse.org/package/show/utilities/schily
[4] https://tracker.debian.org/media/packages/c/cdrkit/changelog-91.1.11-3.2
[5] https://src.fedoraproject.org/rpms/cdrkit/blob/rawhide/f/cdrkit.spec
> +MKISOFS_CMD=$TST_NEEDS_CMDS
...
next prev parent reply other threads:[~2021-04-01 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-26 1:41 [LTP] [PATCH] fs/iso9660: bugfix for iso9660/isofs.sh zhanglianjie
2021-04-01 11:15 ` Petr Vorel [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-04-02 3:19 zhanglianjie
2021-04-06 10:35 ` Petr Vorel
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=YGWrNBxxmVUgT72/@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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