all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: kde: Add kdelibs.
Date: Wed, 05 Nov 2014 14:18:24 +0100	[thread overview]
Message-ID: <87d2917plr.fsf@gnu.org> (raw)
In-Reply-To: <20141104213754.GA15142@debian> (Andreas Enge's message of "Tue, 4 Nov 2014 22:37:54 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> thanks to Ludovic's help with debugging Qt and dbus, I finally have a working
> recipe for kdelibs that allows me to compile the KDE "Hello, world"
> tutorial at
>   https://techbase.kde.org/Development/Tutorials/First_program

This is good news.  :-)

> It looks like all KDE programs require at least kdelibs, qt, phonon and
> automoc4 to compile; but as these are not needed for running the program,
> it seems inappropriate to make them propagated inputs.

Right, this is not a reason to propagate them.

Perhaps eventually you’ll find it convenient to have a specific build
system with those listed as implicit inputs, though.

> The configure flags
>    "-DCMAKE_SHARED_LINKER_FLAGS=-lQtNetwork -lQtXml"
>    "-DCMAKE_EXE_LINKER_FLAGS=-lQtCore"
> look like bugs in kdelibs to me; but I wonder if reporting them makes sense.

What does it fix?  Would be nice to leave a comment above it.

> Quite a few of the tests fail, and already the first one (which is a simple
> compression and archiver test) hangs at 100% CPU before being killed after
> 1500s. I can try to run all the tests and see whether there is some useful
> output. Otherwise hunting down the test failures looks hopeless.

It would be nice to investigate a bit, but IMO it can be done
incrementally (commit with #:tests? #f and a FIXME, and then see what
can be done.)

> -  #:use-module ((guix licenses) #:select (bsd-2 lgpl2.0+ lgpl2.1 lgpl2.1+ lgpl3+))
> +  #:use-module ((guix licenses) #:select (bsd-2 lgpl2.0 lgpl2.0+ lgpl2.1 lgpl2.1+ lgpl3+))

At this point, it’s probably better to just use #:prefix.  :-)

> +    (inputs
> +     `(("attica" ,attica)
> +       ("automoc4" ,automoc4)
> +       ("bison" ,bison)
> +       ("docbook-xml" ,docbook-xml)
> +       ("docbook-xsl" ,docbook-xsl)
> +       ("flex" ,flex)

I suspect automoc4, bison, flex, and docbook-* should be in
‘native-inputs’.

> +    (synopsis "Main libraries for the KDE desktop")
> +    (description "KDE desktop environment")

Make sure to improve it before committing.

> +    (license lgpl2.0))) ; the libraries; examples are under GPL

It’s version 2.0 only?

Thanks!

Ludo’.

  reply	other threads:[~2014-11-05 13:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 21:37 [PATCH] gnu: kde: Add kdelibs Andreas Enge
2014-11-05 13:18 ` Ludovic Courtès [this message]
2014-11-05 13:49   ` 宋文武
2014-11-05 19:22   ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05 19:50 Federico Beffa
2014-11-05 20:15 ` Ludovic Courtès
2014-11-05 20:28   ` Eric Bavier
2014-11-05 21:00     ` Federico Beffa
2014-11-05 21:18       ` Andreas Enge
2014-11-05 23:20         ` Andreas Enge
2014-11-06 11:46           ` Ludovic Courtès
2014-11-06 22:37             ` Andreas Enge
2014-11-06 22:54               ` Andreas Enge
2014-11-06 23:12                 ` Andreas Enge
2014-11-06 23:09               ` Eric Bavier
2014-11-06 23:24                 ` Andreas Enge
2014-11-07  9:20               ` Ludovic Courtès
2014-11-07 14:51                 ` Andreas Enge
2014-11-07 14:59               ` 宋文武
     [not found] <641d5f5d.31e3.14aaea456bc.Coremail.iyzsong@163.com>
2015-01-03  7:20 ` 宋文武
2015-01-03 11:06   ` Andreas Enge
2015-01-04 21:29   ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d2917plr.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --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.