FreeBSD Pkg: rubygem-bcrypt

[Sir l33tname]

> is the application I'm using
Are you at liberty to share which application this is?

> they specify it to the release version

This is kindof not true the latest release is 3.1.13 see:
https://rubygems.org/gems/bcrypt

I think you are talking about that on github the latest version still
points to 3.1.12:
https://github.com/codahale/bcrypt-ruby/releases/latest

Which means not much to my knowledge,
it's just a fancy way to use get a permanent link to the latest version. 

> the bundle install for the application started to fail

Why don't you use bundler to install all dependencies?
Because if you would do that you can easily install 3.1.12.

l33tname

On 11/14/19 9:12 PM, Ben Pratt wrote:
> My reason is the application I'm using specifies a version of the
> bcrypt gem to use and they specify it to the release version.
>
> I'm not sure why they don't have it specified to use the release
> version or newer, possibly because of potential stability issues, but
> after the pkg went to v3.1.13, and I realize this was several months
> ago, the bundle install for the application started to fail.
>
> Ben
>
> On Thu, Nov 14, 2019 at 2:02 PM Sir l33tname <sirl33tname at gmail.com
> <mailto:sirl33tname at gmail.com>> wrote:
>
>     Yeah it would be possible but is there a real reason
>     to not use 3.1.13?
>
>     l33tname
>
>     On 11/14/19 4:16 PM, Ben Pratt wrote:
>     > The FreeBSD pkg rubygem-bcrypt is built based on v3.1.13
>     >
>     (https://svnweb.freebsd.org/ports/head/security/rubygem-bcrypt/Makefile?view=log)
>     > but according
>     to https://github.com/codahale/bcrypt-ruby/releases the
>     > "Latest release" 
>     > (https://github.com/codahale/bcrypt-ruby/releases/latest) is
>     v3.1.12.
>     >
>     > Would it be possible to create the rubygem-bcrypt pkg from
>     v3.1.12 and
>     > if v3.1.13 is needed create a separate rubygem-bcrypt-dev pkg?
>     >
>     > Thank you for the consideration,
>     >
>     > Ben
>