Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Damian Janowski <jano-eWlILCNyKRBBDgjK7y7TUQ@public.gmane.org>
To: "Rainbows! list" <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Rainbows gemspec lists Unicorn with a broad dependency
Date: Thu, 16 Jan 2014 17:13:22 -0200	[thread overview]
Message-ID: <CABAijKEeAyxPS8F4hRXN+veKVwcCaZRkm90PjNijMwbfZASEFA@mail.gmail.com> (raw)

Eric,

Rainbows lists the Unicorn dependency passing an array [1]. I saw that
this is used in the RubyGems documentation, but apparently it's
broken–probably on RubyGems' side.

I did a fresh install of Rainbows 4.3.1 and it installed Unicorn
4.8.0. This combo makes Rainbows not boot due to an exception (someone
trying to call TrueClass#dup).

Maybe the ability to combine both optimistic and strict version
requirements is not worth it?

Thanks.
D.

[1] http://bogomips.org/rainbows.git/tree/rainbows.gemspec#n32
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


             reply	other threads:[~2014-01-16 19:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 19:13 Damian Janowski [this message]
     [not found] ` <CABAijKEeAyxPS8F4hRXN+veKVwcCaZRkm90PjNijMwbfZASEFA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-01-16 19:46   ` Rainbows gemspec lists Unicorn with a broad dependency Eric Wong
     [not found]     ` <20140116194634.GA13492-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2014-01-16 20:00       ` Eric Wong
     [not found]         ` <20140116200053.GA17620-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2014-01-16 21:02           ` Damian Janowski

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://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABAijKEeAyxPS8F4hRXN+veKVwcCaZRkm90PjNijMwbfZASEFA@mail.gmail.com \
    --to=jano-ewlilcnykrbbdgjk7y7tuq@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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://yhbt.net/rainbows.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).