all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Christopher Baines <mail@cbaines.net>
Cc: 34217@debbugs.gnu.org
Subject: [bug#34217] [PATCH 03/11] gnu: Add ruby-ruby-progressbar.
Date: Sun, 3 Feb 2019 22:40:22 +0100	[thread overview]
Message-ID: <20190203224015.0cf8fd3d@alma-ubu> (raw)
In-Reply-To: <20190127114956.26570-3-mail@cbaines.net>

On Sun, 27 Jan 2019 11:49:48 +0000
Christopher Baines <mail@cbaines.net> wrote:

> * gnu/packages/ruby.scm (ruby-ruby-progressbar): New variable.
> ---
>  gnu/packages/ruby.scm | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> diff --git a/gnu/packages/ruby.scm b/gnu/packages/ruby.scm
> index 808b2d8686..15382de017 100644
> --- a/gnu/packages/ruby.scm
> +++ b/gnu/packages/ruby.scm
> @@ -2507,6 +2507,28 @@ rate.")
>      (home-page "https://github.com/paul/progress_bar")
>      (license license:wtfpl2)))
>  
> +(define-public ruby-ruby-progressbar
> +  (package
> +    (name "ruby-ruby-progressbar")

Although we do not have a specific section about Ruby packages, I would
stick to the rules for Python packages:

https://www.gnu.org/software/guix/manual/en/guix.html#Python-Modules

"If a project already contains the word python, we drop this; for
instance, the module python-dateutil is packaged under the names python-dateutil"

Thus, rename the package to just "ruby-progressbar".

Otherwise, LGTM.

Thanks,

Björn

  reply	other threads:[~2019-02-03 21:41 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-27 11:06 [bug#34217] [PATCH 00/11] Add ruby-cucumber along with dependencies and a couple of updates Christopher Baines
2019-01-27 11:49 ` [bug#34217] [PATCH 01/11] gnu: Add ruby-cucumber-wire Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 02/11] gnu: Add ruby-contracts Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 03/11] gnu: Add ruby-ruby-progressbar Christopher Baines
2019-02-03 21:40     ` Björn Höfling [this message]
2019-02-08 18:58       ` Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 04/11] gnu: Add ruby-fuubar Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 05/11] gnu: Add ruby-cucumber-expressions Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 06/11] gnu: Add ruby-mspec Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 07/11] gnu: Add ruby-backports Christopher Baines
2019-01-31  8:53     ` swedebugia
2019-02-01 15:41       ` swedebugia
2019-02-08 19:10         ` Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 08/11] gnu: Add ruby-cucumber-tag-expressions Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 09/11] gnu: ruby-cucumber-core: Update to 3.2.1 Christopher Baines
2019-02-03 22:20     ` Björn Höfling
2019-02-08 18:48       ` Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 10/11] gnu: ruby-gherkin: Update to 5.1.0 Christopher Baines
2019-01-27 11:49   ` [bug#34217] [PATCH 11/11] gnu: Add ruby-cucumber and ruby-aruba Christopher Baines
2019-01-29 21:44     ` swedebugia
2019-01-30 12:56       ` Ricardo Wurmus
2019-01-30 16:11         ` swedebugia
2019-01-30 16:22           ` swedebugia
2019-01-31  8:43             ` swedebugia
2019-02-08 18:46               ` Christopher Baines
2019-02-03 22:18     ` Björn Höfling
2019-02-03 23:26       ` Ricardo Wurmus
2019-02-08 17:19         ` Christopher Baines
2019-02-08 17:19       ` Christopher Baines
2019-02-08 19:02         ` Björn Höfling
2019-02-03 21:03   ` [bug#34217] [PATCH 01/11] gnu: Add ruby-cucumber-wire Björn Höfling
2019-02-08 19:05     ` Christopher Baines
2019-01-28  5:52 ` [bug#34217] [PATCH 00/11] Add ruby-cucumber along with dependencies and a couple of updates swedebugia
2019-02-03 22:21 ` Björn Höfling
2019-02-14 21:57 ` bug#34217: Ruby on Rails Christopher Baines

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=20190203224015.0cf8fd3d@alma-ubu \
    --to=bjoern.hoefling@bjoernhoefling.de \
    --cc=34217@debbugs.gnu.org \
    --cc=mail@cbaines.net \
    /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.