unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Ben Woodcroft <b.woodcroft@uq.edu.au>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: [PATCH] Add rubygems updater.
Date: Tue, 5 Jan 2016 15:56:31 +0100	[thread overview]
Message-ID: <idjoad0gjmo.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <568BCBDB.1010308@uq.edu.au>


Ben Woodcroft <b.woodcroft@uq.edu.au> writes:

>>> We could even default this to the expected name of the library guessed
>>> from the name of the package when #:import is not given. However, this
>>> would unfortunately break packages that have been written outside of
>>> Guix, so I imagine you don't feel this is a good idea.
>> We could choose the package name as a default value, but often that’s
>> not going to work, notably because of the “ruby-” prefix.
>>
>> WDYT?
> Removing the "ruby-" from the package name sounds like a reasonable 
> default, but won't work every time because some imports use underscores 
> where some use dashes e.g. "minitest-pretty_diff".

For R packages we’re using something like this

        (properties `((upstream-name . "gridExtra")))

to hold the upstream name.  The Guix package is called “r-gridextra”.
Maybe that’s acceptable for Ruby packages too?

~~ Ricardo

  reply	other threads:[~2016-01-05 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  8:27 [PATCH] Add rubygems updater Ben Woodcroft
2016-01-01  9:28 ` Pjotr Prins
2016-01-01 11:18   ` Ben Woodcroft
2016-01-01 11:42     ` Pjotr Prins
2016-01-01 18:17     ` Ludovic Courtès
2016-01-02  0:11       ` Ben Woodcroft
2016-01-02 20:54         ` Ludovic Courtès
2016-01-03  0:50           ` Ben Woodcroft
2016-01-03 14:06             ` Ludovic Courtès
2016-01-05 13:57               ` Ben Woodcroft
2016-01-05 14:56                 ` Ricardo Wurmus [this message]
2016-01-08 18:18                 ` Ludovic Courtès
2016-01-02  3:43       ` Pjotr Prins

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=idjoad0gjmo.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=b.woodcroft@uq.edu.au \
    --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).