unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add gparted.
Date: Sat, 28 May 2016 20:34:19 +0200	[thread overview]
Message-ID: <87r3cmxc9g.fsf@gnu.org> (raw)
In-Reply-To: <20160528161855.GC16585@jasmine>

Hello Leo,

Thank you for your quick response.

Leo Famulari writes:

> On Sat, May 28, 2016 at 05:52:16PM +0200, Roel Janssen wrote:
>> Dear Guix,
>> 
>> I wonder if my ChangeLog-format commit message is OK this way.
>
> How about wording it as in bf50f7b5870? I don't think it's necessary to
> list the affected packages if it applies to the entire module.

Right.  I had looked for a similar change but could not find one.
Thanks for pointing this one out.

Would it perhaps be better if I split the license prefix changes and
the addition of gparted in two separate patches?

>> Also, is it OK to push this patch for GParted?  To avoid a name
>> collision for 'zlib' (both a license and a package), I added the
>> usual 'license:' prefix to the other packages in this file.
>
> Okay!
>
>> * gnu/packages/disk.scm (gparted): New variable.
>> (parted, fdisk, ddrescue, dosfstools, sdparm, idle3-tools): Avoid ambiguity by
>> adding a prefix to license symbols.
>
> It runs and finds my partitions! I didn't try to actually do anything...

I tested with a USB drive.  I could create a new partition table and a
new partition.

>> +    (arguments
>> +     `(#:tests? #f ; Tests require a network connection.
>
> Is it just a small subset of the tests that require the network? Maybe
> we could disable only those tests?

It seems all tests need to download DTDs from various places on the
internet.  The tests are related to the use of Scrollkeeper (which I
disabled).

As far as I can see there are no unit tests for the actual code.

>> +       #:configure-flags '("--disable-scrollkeeper")))
>
> I'm not sure what this means. Can you leave a comment explaining it?

Of course!  I'm not completely familiar with Scrollkeeper (although I
also wrote a package recipe for it), but what I understand is that it is
a program to manage various formats of documentation, and keep a central
database that links to various forms of documentation.

I added the following comment, but I think explaining the ins and outs of
Scrollkeeper goes too far.  Is the comment good enough?

+       ;; We don't use scrollkeeper elsewhere, so disable updating the
+       ;; scrollkeeper database with documentation from GParted.
+       #:configure-flags '("--disable-scrollkeeper")))

>> +    (inputs
>> +     `(("util-linux" ,util-linux)
>
> Since util-linux is just a mish-mash of miscellaneous utilities, I like
> it when packagers leave a hint of what it's being used for, either in a
> comment, or by naming it after the used library, as in the jack-1
> package.

I followed the example of jack-1 here, because for GParted, it's also
libuuid it takes from the util-linux package.

Kind regards,
Roel Janssen

  reply	other threads:[~2016-05-28 18:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-28 15:52 [PATCH] gnu: Add gparted Roel Janssen
2016-05-28 16:18 ` Leo Famulari
2016-05-28 18:34   ` Roel Janssen [this message]
2016-05-28 19:15     ` Alex Kost
2016-05-28 19:28     ` Leo Famulari
2016-05-28 19:41       ` Roel Janssen

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=87r3cmxc9g.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).