From: "Thompson, David" <dthompson2@worcester.edu>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] ruby-rake-compiler
Date: Sat, 4 Jul 2015 10:45:54 -0400 [thread overview]
Message-ID: <CAJ=RwfaxTxnByX-vDmc9Gr5v5f-Pc8yVtbc9pyZK29ujZ9cxZA@mail.gmail.com> (raw)
In-Reply-To: <20150704142833.GA14821@thebird.nl>
On Sat, Jul 4, 2015 at 10:28 AM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> On Sat, Jul 04, 2015 at 09:55:57AM -0400, Thompson, David wrote:
>> * Removed the rspec native input. It can be added back in when we can
>> actually run the test suite.
>
> Without rspec it won't build. Alternatively remove tasks/rspec.rake
I was able to build it successfully without it. Is this a runtime
error? I tried this as a quick smoke test and there were no errors:
guix environment --ad-hoc ruby ruby-rake-compiler
--exec="rake-compiler --help"
Am I missing something? Send me a patch if you find an issue.
>> * Fixed license. It's actually the Expat license, which is verrrrry
>> similar to the X11 license.
>
> OK. Not too clear on the difference...
There's an extra clause in the X11 license that is not in the Expat
license. Wikipedia has a blurb about it:
https://en.wikipedia.org/wiki/MIT_License#Various_versions
>> > David: there are quite a few modules now that build gems through 'rake
>> > gem'. Would it be an idea to try that by default when there is no
>> > gemspec file?
>>
>> Yes, I think that would be a good change. Want to write a patch that
>> does that and updates all of the relevant package recipes?
>
> I'll give it a shot soon.
Cool. Should be an easy patch to the build phase. :)
- Dave
prev parent reply other threads:[~2015-07-04 14:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 13:08 [PATCH] ruby-rake-compiler Pjotr Prins
2015-07-04 13:55 ` Thompson, David
2015-07-04 14:28 ` Pjotr Prins
2015-07-04 14:45 ` Thompson, David [this message]
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='CAJ=RwfaxTxnByX-vDmc9Gr5v5f-Pc8yVtbc9pyZK29ujZ9cxZA@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.