all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: David Craven <david@craven.ch>, guix-devel <guix-devel@gnu.org>
Subject: Re: [WIP v0.1 0/8] KDE framework 5, tier 1
Date: Sun, 31 Jul 2016 18:33:15 +0200	[thread overview]
Message-ID: <f577cb3b-8cec-5d59-60a5-4a9fd338d68c@crazy-compilers.com> (raw)
In-Reply-To: <CAL1_imn3DMKTbx5+Gn6khC_gQwLsriRy433DV3z13kp3vbphSQ@mail.gmail.com>

Am 30.07.2016 um 00:37 schrieb David Craven:
> Are you still working on these patches?

Unfortunatly I have not time ATM for working on this. Feel free to pick
up and complete it. (I'd be happy if you'd take over :-)

Please note there are more branches (kf5-tier-2, kde-tier-3, kde-tier-4,
kf5-porting-aids) where I prepared packages for the other tiers.

For kapidocs the requirements where not clear. I asked the current
maintainer about the requirements and he answered: "the only
dependencies are python-yaml, jinja2 and doxygen. I updated the readme
file with required/optional dependencies"

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  parent reply	other threads:[~2016-07-31 16:33 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
2016-07-31 16:36   ` Hartmut Goebel
2016-07-31 16:33 ` Hartmut Goebel [this message]
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=f577cb3b-8cec-5d59-60a5-4a9fd338d68c@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --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.