unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Thomas Schmitt <scdbackup@gmx.net>
Cc: 28398@debbugs.gnu.org
Subject: [bug#28398] Xfburn
Date: Fri, 01 Dec 2017 15:13:21 +0100	[thread overview]
Message-ID: <87k1y6fse6.fsf@gnu.org> (raw)
In-Reply-To: <2046678405415120597@scdbackup.webframe.org> (Thomas Schmitt's message of "Wed, 29 Nov 2017 12:40:43 +0100")

Hi Thomas,

"Thomas Schmitt" <scdbackup@gmx.net> skribis:

> ng0 wrote:
>> I've applied your suggestions
>> and the ones Christopher had a while back in this new version
>> of the patches.
>
> The inappropriate word "mastering" is still in one of the two description
> texts in the libburn patch
>
>> +    (synopsis "Library for reading and writing optical discs")
>> +    (description
>> +     "Libburn is a library for reading, mastering and writing optical discs.
>
>
> (It is also still in the description of the current Debian package. But
>  that's only due to the long release cycle. The next Debian package will
>  state what is committed by
>    https://anonscm.debian.org/viewvc/pkg-libburnia/trunk/libburn/debian/control?r1=428&r2=430
> )

For the record, for GNU packages we stick to the GNU description as
maintained in the Womb and ‘guix lint’ makes sure we do:

  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?  If not, can you provide a
suggestion?

> GNU xorriso versus libisoburn's xorriso:
>
> The only known application of libisofs' ACL capabilities is xorriso. It can
> record ACLs as part of backups and restore them back to disk. Operating
> systems are supposed to ignore the ACL info when mounting and reading
> libisofs made filesystems.
>
> Guix currently packages GNU xorriso, which brings own source copies of
> libburn, libisofs, libisoburn, and libjte.
>
> When libburn and libisofs are established as Guix packages and the decision
> is made that Debian's Jigdo ISO download mechanism is not desired, one should
> consider to package libisoburn and to install its dynamically linked xorriso
> binary.

Indeed, we should do that.

> Reason for the existence of GNU xorriso is mainly that it can be compiled
> and installed by a normal user without interfering with system-wide installed
> libburn and libisofs. This provides freedom from distro decisions and delays.

As package maintainers our choice is to *not* use bundled software in
such cases, though.  Is it the only difference between the two xorrisos?

Thanks for your feedback, it’s useful guidance!

Ludo’.

  parent reply	other threads:[~2017-12-01 14:14 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 [this message]
2017-12-01 16:06                 ` Thomas Schmitt
2017-12-04 14:06                   ` Ludovic Courtès
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=87k1y6fse6.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).