From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Schmitt <scdbackup@gmx.net>
Cc: 28398@debbugs.gnu.org
Subject: [bug#28398] Xfburn
Date: Mon, 04 Dec 2017 15:06:37 +0100 [thread overview]
Message-ID: <87bmjeoadu.fsf@gnu.org> (raw)
In-Reply-To: <28756780424908815522@scdbackup.webframe.org> (Thomas Schmitt's message of "Fri, 01 Dec 2017 17:06:08 +0100")
"Thomas Schmitt" <scdbackup@gmx.net> skribis:
> Ludovic Courtès wrote:
>> http://cvs.savannah.gnu.org/viewvc/*checkout*/womb/gnumaint/pkgblurbs.txt
>> However in this case our Xorriso description seems to differ.
>> Are you OK with the one in pkgblurbs.txt above?
>
> I'm not sure whether the last sentence could be misleading:
> "xorriso can then be used to copy files directly into or out of ISO files."
>
> "ISO files" should be "ISO filesystems", in any case.
Indeed, fixed.
[...]
>> As package maintainers our choice is to *not* use bundled software in
>> such cases, though. Is it the only difference between the two xorrisos?
>
> Feature- and bug-wise: yes.
> There is the built-in copy of libjte in GNU xorriso, which one would have
> to offer libisoburn at configure-, build-, and run-time, in order to get
> the same capability of creating Debian .jigdo and .template files.
> See also https://www.debian.org/CD/jigdo-cd/
>
> Name-wise there are problems with some from-source distros which have
> a 1:1 relationship between source package and installed set of binaries.
> They are unable to offer a package named "xorriso" but only its upstream
> package "libisoburn".
> (I could have changed this by splitting up the three upstream tarballs
> into six, some years ago. But i did not like the idea much and my then
> Debian Developer hated it thoroughly. Meanwhile it would cause work in
> too many distros.)
> Afaik, the FreeBSD port of libisoburn is named "xorriso".
> Archlinux has a "Provides:" header where its "libisoburn" package
> advertises "xorriso, xorriso-tcltk".
>
> Any difference results from automatic creation of GNU xorriso from the
> library sources by
> https://dev.lovelyhq.com/libburnia/libisoburn/raw/master/xorriso/make_xorriso_standalone.sh
> It makes changes about:
> - Build system files: bootstrap, configure.ac, Makefile.am, version.h.in
> - Documentation files: CONTRIBUTORS, README, COPYRIGHT, COPYING, AUTHORS
> - Program id message and license statement control macro in xorriso/xorriso.h
I see.
Thanks for explaining!
Ludo’.
next prev parent reply other threads:[~2017-12-04 14:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 14:15 [bug#28398] Xfburn ng0
2017-09-15 11:41 ` ng0
2017-09-30 15:14 ` Christopher Baines
2017-09-30 15:33 ` ng0
2017-09-30 17:33 ` Christopher Baines
2017-10-01 8:34 ` Thomas Schmitt
2017-10-01 10:20 ` Thomas Schmitt
2017-11-29 9:14 ` ng0
2017-11-29 11:40 ` Thomas Schmitt
2017-11-29 14:37 ` ng0
2017-12-01 14:13 ` Ludovic Courtès
2017-12-01 16:06 ` Thomas Schmitt
2017-12-04 14:06 ` Ludovic Courtès [this message]
2017-12-11 9:58 ` ng0
2017-12-11 11:02 ` Thomas Schmitt
2017-12-29 16:39 ` ng0
2018-02-01 23:04 ` bug#28398: Xfburn Christopher Baines
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bmjeoadu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28398@debbugs.gnu.org \
--cc=scdbackup@gmx.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).