svn commit: r521738 - head/devel/rubygem-rspec

[Adam Weinberger]

On Wed, Jan 1, 2020 at 8:49 PM Po-Chuan Hsieh <sunpoet at freebsd.org> wrote:
>
> On Thu, Jan 2, 2020, 01:05 Adam Weinberger <adamw at adamw.org> wrote:
>>
>> On Wed, Jan 1, 2020 at 9:31 AM Sunpoet Po-Chuan Hsieh
>> <sunpoet at freebsd.org> wrote:
>> >
>> > Author: sunpoet
>> > Date: Wed Jan  1 16:31:26 2020
>> > New Revision: 521738
>> > URL: https://svnweb.freebsd.org/changeset/ports/521738
>> >
>> > Log:
>> >   Update version requirement of RUN_DEPENDS
>> >
>> >   - Take maintainership
>>
>> I have to ask: Why are you taking maintainership of all these
>> community-maintained modules? You're already the main person on ruby@,
>> so grabbing maintainership when you update a port simply deprives
>> others of the ability to contribute to them.
>>
>> Like, for example, that this rspec commit missed the fact that 3 of
>> the updates were already stale. I would have done the bumps myself,
>> but cannot do so now. (Don't get me wrong; I know you always catch
>> them and the updates are coming in the next few days.) But I urge you
>> to slow down on maintainership-grabbing from community-maintained
>> modules, unless there's some reason that nobody else should be
>> altering them.
>>
>> # Adam
>
>
> Hi Adam,
>
> The main reason is that the latest rspec* update from 3.8.* to 3.9.0 missed rspec-rails  which was 3.8.2 and requires rspec* ~> 3.8.0. that's why i want to take them and update the RUN_DEPENDS version range.

Ok, thank you for that explanation. As I mentioned, I just wanted to
make sure that you're taking maintainership with a specific objective
in mind.

# Adam


-- 
Adam Weinberger
adamw at adamw.org
https://www.adamw.org