From: ng0 <contact.ng0@cryptolab.net>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Mass-packaging of 300 KDE application prepared - Help required
Date: Sat, 18 Mar 2017 09:34:56 +0000 [thread overview]
Message-ID: <20170318093456.e2h6cnqyqqrv4ji7@abyayala> (raw)
In-Reply-To: <58CA6E7B.30500@crazy-compilers.com>
Hartmut Goebel transcribed 1.7K bytes:
> Hello all,
>
> as promised earlier, I prepared a repository inclusing patches for more
> than 300 KDE packages. I will not have time to work on them, though.
> Others will need to implement the packages based on this preperations.
Wow! Thanks for your work on this!
> The repo contains prepared guix package descriptions for more than 300
> KDE packages. The idea is to take a lot of stupid work from the
> shoulders of those who want to add a KDE package and automatically
> prepare as much as possible.
>
> Prepared are
> - name, version, url, hash
> - synopsis (two variants)
> - description (two variants)
> - license (needs to be verified)
> - inputs and native-inputs
> - store-path of the archive
>
> The synopsis and descriptions are taken from Debian and Mageia, chosen
> by what was easy to access for me.
>
> The license is taken from Debian but needs to be rechecked. Maybe
> OpenSuSE is a good place to look since they seem to have a strong focus
> on this.
>
> The inputs and native-inputs are taken from the `CMakeList.txt` file,
> which I processed and mapped many known requirements to guix's package
> names. For your convenience unprocessed content of the `CMakeList.txt`
> file has been put into the description, so you hopefully find all
> necessary information there.
>
> The repository can be found at
> <https://gitlab.com/htgoebel/guix-kde-package>, detailed description on
> how to work with it is available ins the README there. If you have any
> enhancement requests, please let me know.
>
> (I refained from sending the patches to some mailinglist since it is
> more then 880KB data and more than 300 patches).
>
> --
> Regards
> Hartmut Goebel
>
> | Hartmut Goebel | h.goebel@crazy-compilers.com |
> | www.crazy-compilers.com | compilers which you thought are impossible |
>
>
next prev parent reply other threads:[~2017-03-18 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 12:11 Preparing mass-packaging of 170 KDE application - hwo to do? Hartmut Goebel
2016-11-27 2:51 ` 宋文武
2016-11-27 21:10 ` Ludovic Courtès
2016-12-04 19:59 ` Preparing mass-packaging of 338 KDE application - how " Hartmut Goebel
2016-12-04 20:27 ` Efraim Flashner
2016-12-05 21:10 ` Ludovic Courtès
2017-03-16 10:52 ` Mass-packaging of 300 KDE application prepared - Help required Hartmut Goebel
2017-03-18 9:34 ` ng0 [this message]
2017-03-18 14:13 ` Ludovic Courtès
2017-03-18 14:21 ` John Darrington
2017-03-19 16:00 ` Ludovic Courtès
2017-03-19 16:27 ` John Darrington
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=20170318093456.e2h6cnqyqqrv4ji7@abyayala \
--to=contact.ng0@cryptolab.net \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).