guix-devel
[Top][All Lists]
Advanced

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

Re: Bring KDE into Guix easily


From: Maxime Devos
Subject: Re: Bring KDE into Guix easily
Date: Sun, 31 Jan 2021 17:50:48 +0100
User-agent: Evolution 3.34.2

On Sun, 2021-01-31 at 17:15 +0100, Hartmut Goebel wrote:
> Hello everybody,
> 
> are you interested in getting KDE into Guix?
> 

Not much of a KDE user myself (except kcachegrind, a drawing
application I forgot the name of and manuskript), but more packages
are nice!
> I prepared a repo providing everything to make this easy:
> 
> Guix package descriptions for another about 100 KDE packages
> 
> scripts to ease adding the package definition to the respective 
> gnu/packages/*.scm file, including commit and commit-message
> 
> Lists about KDE applications per group (education, pim, office, etc.) to work 
> on.
> 
> Just check out 
> https://gitlab.digitalcourage.de/htgoebel/guix-kde-package/-/blob/master/README.md
>  for how easy it is.
> 
> If you have any question, please don't hesitate to contact me.
> 

Some things to improve:
* Some scripts have missing copyright and license headers
   (00-add.sh, 00-test-gui-app.sh).

* I don't see any license information on pkgs/*.scm.
  It's sort of implied these are GPLv3, as Guix itself
  is GPLv3+, but it isn't clear if you would allow GPLv3+
  as well.

* IANAL, but taking synopsises and descriptions
  from external sources (Debian, Mageia) seems
  without mentioning the copyright holder, license
  and author seems suspect for me. Maybe it's legally
  ok here, but best include attribution somewhere,
  and write your reasoning for why inclusion is ok
  somewhere.

My proposal on how to go forward is:
* Please address previous three issues.
* if someone wants a particular KDE package in Guix,
  they can submit an appropriate patch to Guix using
  the repository, after testing whether it works.
* many KDE packages are not up to date  (guix refresh --type=kde).
  These probably need to be updated. I don't know what
  the recommended way for such a change is.
  (How to verify whether no new issues are introduced,
  etc.)

Maxime

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

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