From: Ben Woodcroft <b.woodcroft@uq.edu.au>
To: Frederick Muriithi <fredmanglis@gmail.com>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: ruby-net-http-digest-auth: Add new package
Date: Thu, 17 Nov 2016 20:56:02 +1000 [thread overview]
Message-ID: <1d9d1ec0-e95f-26c9-dcd7-fe01bd913cab@uq.edu.au> (raw)
In-Reply-To: <CALjrZwZu-jyQf6h+Sbf9jyPzY04YZ7N=qid2xAZVPfah2dPDrQ@mail.gmail.com>
Hi Frederick, thanks for the updated patch.
I didn't see any functional issues with this patch, but I had some
trouble testing this out - can I ask how to test it? My problem was
simply that I didn't know of a http-only server with this authentication
method. I ask because the last commit to the development repository was
in 2013.
Below is some minor points about the patch. If you are happy with them
and we are confident in the testing then I'll push with these changes.
Do not worry about sending an updated patch.
On 17/11/16 01:57, Frederick Muriithi wrote:
> gnu: ruby-net-http-digest-auth: Add new package
>
> * gnu/packages/ruby.scm (ruby-net-http-digest-auth): Added a new
> package definition
I changed the commit message to the following as conventional:
gnu: Add ruby-net-http-digest-auth.
* gnu/packages/ruby.scm (ruby-net-http-digest-auth): New variable.
> ---
> gnu/packages/ruby.scm | 24 ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm
> index 42beda3..ab10664 100644
> --- a/gnu/packages/ruby.scm
> +++ b/gnu/packages/ruby.scm
> @@ -4179,3 +4179,27 @@ patterns.")
> libraries for compiling Ruby native extensions.")
> (home-page "https://github.com/ruby-gnome2/pkg-config")
> (license license:lgpl2.0+)))
> +
> +(define-public ruby-net-http-digest-auth
> + (package
> + (name "ruby-net-http-digest-auth")
> + (version "1.4")
> + (source
> + (origin
> + (method url-fetch)
> + (uri (rubygems-uri "net-http-digest_auth" version))
> + (sha256
> + (base32
> + "14801gr34g0rmqz9pv4rkfa3crfdbyfk6r48vpg5a5407v0sixqi"))))
> + (build-system ruby-build-system)
> + (inputs
> + `(("ruby-hoe" ,ruby-hoe)))
This should be a native-input.
> + (synopsis
> + "Library for HTTP Digest Authentication based on RFC 2617")
In general we make a habit of keeping this all on one line. How about this?
(synopsis "RFC 2617 HTTP digest authentication library")
> + (description
> + "This library implements HTTP's Digest Authentication scheme in
> ruby.
> +This enables you to use the Digest Authentication scheme,
> +over the more insecure Basic Authentication scheme")
My science-based bias against personal pronouns perhaps, how does this
sound?
(description
"This library implements HTTP's digest authentication scheme based on
RFC 2617. This enables the use of the digest authentication scheme instead
of the more insecure basic authentication scheme.")
> + (home-page
> + "http://github.com/drbrain/net-http-digest_auth")
Best to keep that on one line.
> + (license license:expat)))
Thanks.
ben
next prev parent reply other threads:[~2016-11-17 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 15:57 [PATCH] gnu: ruby-net-http-digest-auth: Add new package Frederick Muriithi
2016-11-17 10:56 ` Ben Woodcroft [this message]
2016-11-17 11:47 ` Frederick Muriithi
2016-11-19 5:20 ` Ben Woodcroft
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=1d9d1ec0-e95f-26c9-dcd7-fe01bd913cab@uq.edu.au \
--to=b.woodcroft@uq.edu.au \
--cc=fredmanglis@gmail.com \
--cc=guix-devel@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 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).