[146550] trunk/dports/devel/libgit2/Portfile

[David Evans]

On 3/14/16 1:25 PM, Sean Farley wrote:
> 
> David Evans <devans at macports.org> writes:
> 
>> On 3/14/16 10:53 AM, Sean Farley wrote:
>>>
>>> David Evans <devans at macports.org> writes:
>>>
>>>> On 3/11/16 2:55 PM, sean at macports.org wrote:
>>>>> Revision
>>>>>     146550 <https://trac.macports.org/changeset/146550>
>>>>> Author
>>>>>     sean at macports.org
>>>>> Date
>>>>>     2016-03-11 14:55:34 -0800 (Fri, 11 Mar 2016)
>>>>>
>>>>>
>>>>>       Log Message
>>>>>
>>>>> libgit2: update to 0.24.0
>>>>>
>>>>>
>>>>>       Modified Paths
>>>>>
>>>>>   * trunk/dports/devel/libgit2/Portfile <#trunkdportsdevellibgit2Portfile>
>>>>>
>>>>>
>>>>>       Diff
>>>>>
>>>>>
>>>>>         Modified: trunk/dports/devel/libgit2/Portfile (146549 => 146550)
>>>>>
>>>>> --- trunk/dports/devel/libgit2/Portfile 2016-03-11 22:55:33 UTC (rev 146549) +++ trunk/dports/devel/libgit2/Portfile
>>>>> 2016-03-11 22:55:34 UTC (rev 146550) @@ -8,8 +8,7 @@ cmake.out_of_source yes # don't forget to update libgit2-glib as
>>>>> well -github.setup libgit2 libgit2 0.23.4 v -revision 4 +github.setup libgit2 libgit2 0.24.0 v categories devel
>>>>> platforms darwin maintainers juanrgar devans openmaintainer
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> I've been holding off on updating this port to version 0.24.0 due to the fact that the current version of libgit2-glib
>>>> will only build with the previous version.
>>>
>>> And other ports must suffer for some lame glib fork?
>>
>>>
>>>> Would appreciate it if you would revert this update until a compatible version is available upstream.
>>>
>>> Now pygit2 is broken. Thanks for wrecking my work day. If you must have
>>> an older version, the usual way to create another port (e.g. libgit23).
>>
>> I note that you updated the version of libgit2 without checking with me or checking the compatibility of
>> dependents other than those you are interested in. I would have told you there was an issue that was blocking
>> the upgrade.
>>
>> This is the second time that you've arbitrarily modified this port without consultation or regard for the consequences
>> to other ports.
>>
>> pygit2 is only broken because you updated to a version that requires 0.24.0.  It was working fine with the previous version.
>>
>> I expect the problem with libgit2-glib to be resolved shortly.  If not, of course, I will do as you say and create a
>> compatibility version of libgit2 but as of now that doesn't seem necessary.
>>
>> I'm glad to work with you to come to a resolution of this problem that doesn't cause breakage of any ports.  However,
>> I've got to say that I'm a bit put off by your arrogant attitude and your unwillingness to work cooperatively with others.
> 
> If I come off as arrogant, my apologies. I like to move fast and this
> makes working with me difficult.
> 
> For what it's worth, I'm testing a script that automatically updates a
> port so we can (potentially) have a bot that tries to update every
> outdated port and report what breaks. This caused me to miss your
> comment.
> 
> But I understand that not many people like working with me and my
> efforts are rarely appreciated. Though I still think libgit2-glib is a
> sorry excuse for a project.
> 

I'm sorry for being blunt about it as well but you hit me at the wrong moment.  No hard feelings I hope.

If you have specific suggestions for improvements to this project, I'm sure the upstream developers will be glad to hear
about it.

In the meantime, it is a required dependency of gitg, part of the GNOME 3 application distribution.  Unstable release
3.19.92 (3.20 rc) is occuring this week swiftly followed by the final 3.20 release next week. I expect the libgit2-glib
problem to be remedied by then at the latest.  I'll update libgit2 as soon as it is.

If you have further concerns about the upgrade please feel free to file a ticket so we can track progress of the issue.

Thanks for your forebearance.