unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / Atom feed
From: Pirate Praveen <praveen@onenetbeyond.org>
To: Eric Wong <e@80x24.org>, Hleb Valoshka <375gnu@gmail.com>
Cc: debian-ruby <debian-ruby@lists.debian.org>, unicorn-public@bogomips.org
Subject: Re: trying to update unicorn to 5.1, build failure: VERSION= must be specified
Date: Thu, 3 Nov 2016 21:16:10 +0530
Message-ID: <2068da61-0ff0-4653-4aa5-598c46354c6a@onenetbeyond.org> (raw)
In-Reply-To: <20161028002315.GA15205@starla>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Friday 28 October 2016 05:53 AM, Eric Wong wrote:
> I understand olddoc may not be worth the effort to package in
> Debian.  (I already tried to reduce dependencies in olddoc
> compared to wrongdoc, but a package is a package...)
> 
> Anyways, I suggest you guys grab the generated gemspec from the
> Rubygem or tar.gz.  You already seem to be doing that with NEWS
> and the manpages to avoid a build-dep on pandoc(*).

We are already using the rubygems.org .gem file and it has olddoc.

> Maybe the gemspec in git could have olddoc become optional, too,
> while still remaining DRY.  The email address for the public
> mailing list is already specified in multiple places, so maybe
> over-DRY-ing isn't worth it...

If you can make it optional that would be great. For now I've just
patched out the gemspec to not use olddoc. The patch and fix in rules is
ugly.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

  reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1d5eacb-b6a2-be96-34aa-fe061a194a62@onenetbeyond.org>
     [not found] ` <CAAB-Kcnwzc8Tcszv3FCPkyJRKRCsHRH6k_qBhKfBpSODxqKy5g@mail.gmail.com>
2016-10-28  0:23   ` Eric Wong
2016-11-03 15:46     ` Pirate Praveen [this message]
2017-03-23 23:34       ` [PATCH] gemspec: remove olddoc from build dependency Eric Wong

Reply instructions:

You may reply publically 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://bogomips.org/unicorn/

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

  git send-email \
    --in-reply-to=2068da61-0ff0-4653-4aa5-598c46354c6a@onenetbeyond.org \
    --to=praveen@onenetbeyond.org \
    --cc=375gnu@gmail.com \
    --cc=debian-ruby@lists.debian.org \
    --cc=e@80x24.org \
    --cc=unicorn-public@bogomips.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

unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help

Archives are clonable:
	git clone --mirror https://bogomips.org/unicorn-public
	git clone --mirror http://ou63pmih66umazou.onion/unicorn-public

Newsgroups are available over NNTP:
	nntp://news.public-inbox.org/inbox.comp.lang.ruby.unicorn
	nntp://ou63pmih66umazou.onion/inbox.comp.lang.ruby.unicorn

 note: .onion URLs require Tor: https://www.torproject.org/

AGPL code for this site: git clone https://public-inbox.org/ public-inbox