all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Brant Gardner" <brantcgardner@brantware.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 35086@debbugs.gnu.org
Subject: [bug#35086] [PATCH] New package file for BOINC client & server
Date: Wed, 10 Apr 2019 16:39:22 -0400	[thread overview]
Message-ID: <47063553-553c-461d-abce-0f6732bc84ac@www.fastmail.com> (raw)
In-Reply-To: <87zhoxc335.fsf@gnu.org>

Good afternoon;

On Wed, Apr 10, 2019, at 10:06, Ludovic Courtès wrote:
> Hello Brant,
> 
> "Brant Gardner" <brantcgardner@brantware.com> skribis:
> 
> > This is my first submission for contributing to Guix, so any feedback or advice is welcomed!
> 
> Thanks for joining!
> 
> I have some suggestions below, but overall it\x19s a great start!
> 
> > From 2946bd1c83a2ea224841d22463992be599dfc385 Mon Sep 17 00:00:00 2001
> > From: Brant Gardner <brantcgardner@brantware.com>
> > Date: Tue, 2 Apr 2019 11:09:45 -0500
> > Subject: [PATCH] Added distributed.scm
> >
> > New package file for BOINC and other distributed-computing projects.  This
> > initial file just includes boinc-client and boinc-server, both at version
> > 7.14.2.
> 
> The convention is to write commit logs in \x1cChangeLog format\x1d, as
> described at:
> 
>   https://www.gnu.org/prep/standards/html_node/Change-Logs.html
> 
> But you can simply look at \x18git log\x19 and mimic what you see.  (You might
> also want to take a look at
> <https://gnu.org/software/guix/manual/en/html_node/Submitting-Patches.html>
> if you haven\x19t already.)
> 

Yeah, I was following the guide but I had accidentally already committed before I read the part on commit log format.  I'll make a new one that follows the pattern this time.

> As for the module name, what about boinc.scm instead?  \x1cDistributed\x1d
> sounds a bit too generic to me.
>

Done :)
 
> > +++ b/gnu/packages/distributed.scm
> > @@ -0,0 +1,119 @@
> > +;;; GNU Guix --- Functional package management for GNU
> > +;;; Copyright .© 2014, 2015 Ludovic Court.¨s <ludo@gnu.org>
> > +;;; Copyright .© 2016, 2017, 2018, 2019 Efraim Flashner <efraim@flashner.co.il>
> > +;;; Copyright .© 2018 Tobias Geerinckx-Rice <me@tobias.gr>
> > +;;; Copyright .© 2018 Mathieu Othacehe <m.othacehe@gmail.com>
> 
> It should be just you here.  :-)
> 

Got it, done.

> > +  #:use-module (gnu packages autotools)
> > +  #:use-module (gnu packages base)
> > +  #:use-module (gnu packages compression)
> > +  #:use-module (gnu packages databases)
> > +  #:use-module (gnu packages pkg-config)
> > +  #:use-module (gnu packages tls)
> > +  #:use-module (gnu packages curl)
> > +  #:use-module (gnu packages wxwidgets)
> > +  #:use-module (gnu packages gnome)
> > +  #:use-module (gnu packages gtk)
> > +  #:use-module (gnu packages perl)
> > +  #:use-module (gnu packages sqlite)
> > +  #:use-module (gnu packages python)
> > +  #:use-module (gnu packages python-xyz))
> 
> I think you can trim this list.
> 

I don't believe so, I arrived at that list via 'build, fail on missing dependency, find it, add it, repeat'.  This was the result - I know it's long and varied but it appears to be correct unless I misunderstand how to properly do dependencies.

> > +    (synopsis "BOINC lets you help cutting-edge science research using your computer")
> 
> What about something like \x1cContribute computing power to research projects\x1d?
> 

Sure thing - but to be clear, these aren't my words.  I copied/pasted from the project homepage 'About' section.  I figured they wrote it, they knew how to describe it.

> > +    (description "BOINC is a platform for high-throughput computing on a large
> > +scale (thousands or millions of computers).  It can be used for volunteer
> > +computing (using consumer devices) or grid computing (using organizational
> > +resources).  It supports virtualized, parallel, and GPU-based applications.
> > +
> > +BOINC is distributed under the LGPL open source license.  It can be used for
> > +commercial purposes, and applications need not be open source.")
> 
> This last paragraph is unnecessary: everything in Guix is free software,
> so we never mention it in descriptions.

Got it, done.

> 
> > +    (synopsis "BOINC lets you help cutting-edge science research using your computer")
> > +    (description "BOINC is a platform for high-throughput computing on a large
> > +scale (thousands or millions of computers).  It can be used for volunteer
> > +computing (using consumer devices) or grid computing (using organizational
> > +resources).  It supports virtualized, parallel, and GPU-based applications.
> 
> It would be nice to have a slightly different synopsis and description
> for the server and for the client.
>

Understood, I'll go over it and try to differentiate them a bit.

> Apart from that it LGTM!  Could you double check that \x18guix lint\x19 is
> happy and send an updated patch?
> 

Hmm.  I already ran 'guix lint' and did everything it advised except for these:

gnu/packages/boinc.scm:45:12: boinc-client@7.14.2: the source URI should not be an autogenerated tarball
gnu/packages/boinc.scm:80:12: boinc-server@7.14.2: the source URI should not be an autogenerated tarball

I understand what it doesn't like, but not what it wanted me to do instead.  Could you advise?

> Thank you!
> 
> Ludo\x19.
>

--
Brant Gardner

  reply	other threads:[~2019-04-10 20:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-02 16:24 [bug#35086] [PATCH] New package file for BOINC client & server Brant Gardner
2019-04-10 15:06 ` Ludovic Courtès
2019-04-10 20:39   ` Brant Gardner [this message]
2019-04-10 21:27     ` Tobias Geerinckx-Rice
2019-08-06 20:14 ` [bug#35086] BOINC Brian Leung
2019-09-24  6:56   ` bug#35086: BOINC Brian Leung
2019-09-24 12:21     ` [bug#35086] BOINC Brant Gardner

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=47063553-553c-461d-abce-0f6732bc84ac@www.fastmail.com \
    --to=brantcgardner@brantware.com \
    --cc=35086@debbugs.gnu.org \
    --cc=ludo@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.