unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Brasero, or gnome without gnome
Date: Thu, 3 Oct 2013 13:07:44 +0200	[thread overview]
Message-ID: <20131003110744.GB6327@debian> (raw)
In-Reply-To: <87li2bnwf9.fsf@gnu.org>

On Thu, Oct 03, 2013 at 12:24:26AM +0200, Ludovic Courtès wrote:
> :-)  Can’t it use GNU xorriso as the back-end?

I do not think so.

> > And not to start a flame war, but I see it as a real incentive to consider
> > kde packaging...
> I think you’d encounter similar patterns there.

Definitely, I expect the same kinds of problems. But having seen both
k3b and brasero now, I know which one I prefer...

> Besides, while I have nothing against KDE (esp. if someone else does the
> job ;-)), I think we should support GNOME as it is somewhat related to
> GNU.

That is true. But I feel about GNOME as you feel about KDE, and am not overly
motivated to do more work on it, so it would be good if some volunteer
GNOME users stepped forward to take over.

Would it be okay to push the current moderately usable brasero package
so as not to lose the work?

> > As a first step, for qt, I think we might need to get the cmake build
> > system working. Cyril, would you be able to make it work on x86_64,
> > potentially by disabling the failing test in cmake?
> Good news: the failing test no longer fails on x86_64!  That could be a
> result of the ‘ldd’ fix in core-updates.

Excellent news indeed!

Andreas

  reply	other threads:[~2013-10-03 11:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 12:41 Brasero, or gnome without gnome Andreas Enge
2013-10-02 18:02 ` Andreas Enge
2013-10-02 19:32   ` Ludovic Courtès
2013-10-02 20:56     ` Andreas Enge
2013-10-02 21:18       ` Andreas Enge
2013-10-02 22:24         ` Ludovic Courtès
2013-10-03 11:07           ` Andreas Enge [this message]
2013-10-03 11:19             ` Ludovic Courtès
2013-10-04 16:50             ` Aljosha Papsch
2013-10-04 20:01               ` Ludovic Courtès
2013-10-07 19:53               ` Andreas Enge
2013-10-09 17:03                 ` Aljosha Papsch
2013-10-09 20:22                   ` Ludovic Courtès
2013-10-09 23:01                     ` Aljosha Papsch
2013-10-10 12:11                       ` Ludovic Courtès
2013-10-10 20:02                         ` LXDE, was: " Andreas Enge
2013-10-10 12:26                   ` Andreas Enge
2013-10-07 20:11               ` Andreas Enge
2013-10-07 22:00                 ` Ludovic Courtès
2013-10-02 22:17       ` Ludovic Courtès
2013-10-03 11:01         ` Andreas Enge
2013-10-03 11:21           ` Ludovic Courtès
2013-10-03 18:30             ` Andreas Enge
2013-10-03 21:10               ` Ludovic Courtès
2013-10-07 19:48                 ` Andreas Enge
2013-10-02 19:26 ` Cyril Roelandt
2013-10-02 20:53   ` Andreas Enge
2013-10-02 21:48     ` Ludovic Courtès

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=20131003110744.GB6327@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.
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).