From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <john@darrington.wattle.id.au>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Mass-packaging of 300 KDE application prepared - Help required
Date: Sun, 19 Mar 2017 17:00:55 +0100 [thread overview]
Message-ID: <87var52r48.fsf@gnu.org> (raw)
In-Reply-To: <20170318142141.GA16682@jocasta.intra> (John Darrington's message of "Sat, 18 Mar 2017 15:21:41 +0100")
Hi John,
John Darrington <john@darrington.wattle.id.au> skribis:
> On Sat, Mar 18, 2017 at 03:13:25PM +0100, Ludovic Court??s wrote:
> Hi Hartmut,
>
> Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
>
> > 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.
>
> [...]
>
> > 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.
>
> Woow, impressive piece of work!
>
> Thomas Danckaert is visibly interested in KDE ;-), so either Thomas or
> others will cherry-pick from your repo.
>
> I suggest that 300 packages is too much for one person to do.
Yeah you’re right; I didn’t mean to suggest that Thomas would handle all
of them.
> So if there is going to be a joint effort at this I suggest that somehow we
> decide in advance which packages are done by whom.
>
> I'm not sure how best to divide them up, since the lower dependencies will have
> to be done first.
I’m under the impression that it’s usually difficult to assign tasks to
us lazy volunteers. ;-)
My guess is that people will incrementally pick the packages they’re
interested in from Hartmut’s repo.
We’ll see!
Ludo’.
next prev parent reply other threads:[~2017-03-19 16:01 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
2017-03-18 14:13 ` Ludovic Courtès
2017-03-18 14:21 ` John Darrington
2017-03-19 16:00 ` Ludovic Courtès [this message]
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=87var52r48.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=john@darrington.wattle.id.au \
/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).