all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [WIP v0.1 0/8] KDE framework 5, tier 1
Date: Sat, 30 Jul 2016 11:14:39 +0200	[thread overview]
Message-ID: <20160730091439.GA23401@solar> (raw)
In-Reply-To: <CAL1_imn3DMKTbx5+Gn6khC_gQwLsriRy433DV3z13kp3vbphSQ@mail.gmail.com>

Hi David,

On Sat, Jul 30, 2016 at 12:37:27AM +0200, David Craven wrote:
> I see your wip here:
> https://gitlab.com/htgoebel/guix/commits/kf5-tier-1
> Shall we push this past the finish line? Is there anything I can do to help?

work on KDE will definitely be very welcome. During the discussion, Hartmut
said he did not want to work on using the modular Qt instead of the mono-
lithic one. But as I see it, this is a necessary condition to accept the
patches into Guix.

So in a first step, it might also be interesting to complete our Qt packages.

I would suggest to order the packages in kde-frameworks.scm according to the
different "tiers", and to add a comment when a new tier is started, similarly
to the comments in xorg.scm. There is already one package there that was
added before the modular Qt appeared, and which would need to be modified
accordingly.

If you wish to work on any of these topics, please go ahead!

Andreas

  reply	other threads:[~2016-07-30  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29 22:37 [WIP v0.1 0/8] KDE framework 5, tier 1 David Craven
2016-07-30  9:14 ` Andreas Enge [this message]
2016-07-31 16:36   ` Hartmut Goebel
2016-07-31 16:33 ` Hartmut Goebel
2016-07-31 16:38   ` Hartmut Goebel
2016-07-31 18:15   ` David Craven
2016-08-01  8:03     ` Hartmut Goebel
  -- strict thread matches above, loose matches on Subject: below --
2016-06-14 21:15 Hartmut Goebel
2016-06-15 12:22 ` Efraim Flashner
2016-06-17  9:23   ` Hartmut Goebel

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=20160730091439.GA23401@solar \
    --to=andreas@enge.fr \
    --cc=david@craven.ch \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.