From: iyzsong@member.fsf.org (宋文武)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Preparing mass-packaging of 170 KDE application - hwo to do?
Date: Sun, 27 Nov 2016 10:51:27 +0800 [thread overview]
Message-ID: <87shqdeits.fsf@member.fsf.org> (raw)
In-Reply-To: <58382A5D.40403@crazy-compilers.com> (Hartmut Goebel's message of "Fri, 25 Nov 2016 13:11:09 +0100")
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> Hi,
>
> I'm currently working on a script to mass-generate *draft* packages for
> KDE applications. Ca. 170 of them :-) These are the ones listed at
> <https://www.kde.org/applications/>
>
> The idea is to have a draft which can easily be taken and adopted.
> Inputs will be lists at best knowledge (taken from the CMakeLists.txt
> file). Synopsis and description are pre-filled from Debian and Mageia.
Amazing works!
>
> Nevertheless 170 packages are a lot of work, which I would like to
> distribute. Esp. checking the licenses and linting is quite some effort.
>
> Questions:
>
> * To distribute the workload, I'd like to put the drafts somewhere.
> Should I push this into a wip-branch? Or hat else would be an option?
Yes, please. And instead of working on this branch directly and merge
it as a whole, I think we can cherry-pick 1 by 1 from it.
>
> * Should these apps be sorted alphabetically of being grouped
> (development, office, system, education, utilis, …)?
No prefernece here.
Thanks for the works!
next prev parent reply other threads:[~2016-11-27 2:52 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 ` 宋文武 [this message]
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
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=87shqdeits.fsf@member.fsf.org \
--to=iyzsong@member.fsf.org \
--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).