yahns Ruby server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: yahns-public@yhbt.net
Subject: [PATCH] gemspec: make rack a development dependency
Date: Thu, 28 Jan 2016 00:35:01 +0000	[thread overview]
Message-ID: <20160128003501.GA306@dcvr.yhbt.net> (raw)

We don't depend on rack directly, and unicorn 5.1 will make rack
optional.  This seems reasonable for testing, but one day I could
imagine this being more than an HTTP or Rack server...
 yahns.gemspec | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/yahns.gemspec b/yahns.gemspec
index 59c0b9b..0efe287 100644
--- a/yahns.gemspec
+++ b/yahns.gemspec
@@ -22,6 +22,9 @@
   # Matz Ruby release.
   s.add_development_dependency(%q<minitest>, '>= 4.3', '< 6.0')
+  # for Rack::Utils::HeaderHash#each
+  s.add_development_dependency(%q<rack>, '>= 1.1')
   s.homepage = "http://yahns.yhbt.net/README"
   s.licenses = "GPL-3.0+"

                 reply	other threads:[~2016-01-28  0:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

  List information: https://yhbt.net/yahns/README

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

  git send-email \
    --in-reply-to=20160128003501.GA306@dcvr.yhbt.net \
    --to=e@80x24.org \
    --cc=yahns-public@yhbt.net \


* 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


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).