unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Lin Jen-Shin (godfat)" <godfat@godfat.org>
To: Eric Wong <e@80x24.org>
Cc: Pirate Praveen <praveen@debian.org>, unicorn-public@bogomips.org
Subject: Re: Request to follow SemVer/mention it in homepage
Date: Tue, 29 Sep 2015 15:46:49 +0800	[thread overview]
Message-ID: <CAA2_N1voUe1X+k2iGFA-TWhhEhA7JdST9bCVaTcoxQ17WBi64g@mail.gmail.com> (raw)
In-Reply-To: <20150929073650.GA7434@dcvr.yhbt.net>

On Tue, Sep 29, 2015 at 3:36 PM, Eric Wong <e@80x24.org> wrote:
> Pirate Praveen <praveen@debian.org> wrote:
[...]
>> It will help us a lot in maintain rails applications in debian. We
>> like to keep only one version of any app/lib in debian and if you can
>> guarantee Semantic Versioning rails apps using unicorn could declare a
>> looser dependency rather than upto the patch version. Now gitlab
>> defines unicorn ~> 4.8.3 and diaspora defines ~> 4.9.0 If you are
>> following Semantic Versioning they could change it to ~> 4.8 and ~>
>> 4.9 and 4.9.0 will satisfy both. Currently debian has 4.9.0 and it
>> does not match ~> 4.8.3
>
> Tying a Rack app to unicorn is totally, completely wrong and defeats the
> point of Rack.
>
> Honestly, I could understand tying an app to thin with it's EM-specific
> API, but unicorn(!?!?)  Even if an app isn't thread-safe, it should
> still work in passenger, thin, or puma/webrick configured for a
> single-thread...

I guess the issue is that people need to specify which server they're
using in their Gmefile when bundler is used to launch the application.

I don't think it's a good idea to bind to a specific version though.
Upgrading unicorn never breaks anything for me.

p.s. Personally I never liked the idea of semantic versioning either,
unless there's a clearly defined API like Rack's SPEC.

  reply	other threads:[~2015-09-29  7:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29  6:38 Request to follow SemVer/mention it in homepage Pirate Praveen
2015-09-29  7:36 ` Eric Wong
2015-09-29  7:46   ` Lin Jen-Shin (godfat) [this message]
2015-09-29  8:00   ` Pirate Praveen
2015-09-29 19:36     ` Eric Wong
2015-09-30 16:04       ` Pirate Praveen
2015-09-30 19:51         ` Eric Wong
2015-10-01  4:56           ` Pirate Praveen
2015-10-01 11:18             ` Pirate Praveen
2015-10-01 19:06               ` Eric Wong
2015-09-29  9:26   ` Jérémy Lecour
2015-09-29 19:43     ` Eric Wong

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/unicorn/

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

  git send-email \
    --in-reply-to=CAA2_N1voUe1X+k2iGFA-TWhhEhA7JdST9bCVaTcoxQ17WBi64g@mail.gmail.com \
    --to=godfat@godfat.org \
    --cc=e@80x24.org \
    --cc=praveen@debian.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
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/unicorn.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).