[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug#28398] Xfburn

From: ng0
Subject: [bug#28398] Xfburn
Date: Mon, 11 Dec 2017 09:58:37 +0000

Alright, here's the next revision. I've included a new patch to
work in your comments on xorriso (dropping the 2 inputs).

The compiled Xfburn gives me 2 error messages so far:
1. No Drive found (thanks Cpt. Obvious, I have no optical drive here).
2. More concerning:
   Failed to initialize gstreamer transcoder: An error occurred setting 
gstreamer up for transcoding
   (falling back to basic implementation)

Keep in mind that I've tested this from within guile-wm, so
this might be different in XFCE or other environments. I'll
test this later today. I expect XFCE to work in MATE at the
very least, but XFCE-only would be good for starters.

The application itself starts.

Session output on terminal can not be copied right now, I'll
send it in later today if necessary.

Ludovic Courtès transcribed 2.1K bytes:
> "Thomas Schmitt" <address@hidden> skribis:
> > Ludovic Courtès wrote:
> >>*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
> >
> > 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
> >   
> >
> > It makes changes about:
> > - Build system files: bootstrap,,,
> > - Program id message and license statement control macro in 
> > xorriso/xorriso.h
> I see.
> Thanks for explaining!
> Ludo’.

GnuPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588

Attachment: 0001-gnu-Add-libburn.patch
Description: Text document

Attachment: 0002-gnu-Add-libisofs.patch
Description: Text document

Attachment: 0003-gnu-Add-xfburn.patch
Description: Text document

Attachment: 0004-gnu-xorriso-Remove-bzip2-and-libcdio-from-inputs.patch
Description: Text document

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]