On 21 Mar 2018, at 00:31, Ryan Schmidt wrote:
> On Mar 20, 2018, at 09:20, db wrote:
>> macports-announce seems scant to me.
> Intentionally. We only post there when we have something to announce, which
> is seldom.
I still think things like python default and protobuff changes, or enhancements
On 21 March 2018 at 00:13, Ryan Schmidt wrote:
> On Mar 20, 2018, at 09:26, Mojca Miklavec wrote:
>
>> Do you also want to support signatures then?
>> Public keys are pretty long though, but they usually don't change.
>>
>> One example: https://waf.io
>
> I have given no thought to the question of
On Mar 20, 2018, at 09:20, db wrote:
> On 20 Mar 2018, at 14:54, Rainer Müller wrote:
>> https://lists.macports.org/pipermail/macports-announce/
>> https://github.com/macports/macports-base/blob/master/ChangeLog
>
> macports-announce seems scant to me.
Intentionally. We only post there when we
On Mar 20, 2018, at 09:26, Mojca Miklavec wrote:
> On 20 March 2018 at 00:59, Ryan Schmidt wrote:
>> It's been pointed out before than when updating a port to a new version, one
>> should not just update the version and checksums in the portfile; one should
>> also verify at least one of those
On 20 March 2018 at 00:59, Ryan Schmidt wrote:
> It's been pointed out before than when updating a port to a new version, one
> should not just update the version and checksums in the portfile; one should
> also verify at least one of those checksums with the ones published by the
> developers -
On 20 Mar 2018, at 14:54, Rainer Müller wrote:
> https://lists.macports.org/pipermail/macports-announce/
> https://github.com/macports/macports-base/blob/master/ChangeLog
macports-announce seems scant to me. I suggest using a GitHub issue, like
Linuxbrew does, https://github.com/Linuxbrew/brew/i
On 2018-03-20 14:29, db wrote:
> On 20 Mar 2018, at 00:59, Ryan Schmidt wrote:
>> Once that's done, it makes it easier to implement a better "bump" command --
>> one that can use any published checksums and compute the rest, and warn if
>> no checksums were published.
>> https://trac.macports.or
On 20 Mar 2018, at 00:59, Ryan Schmidt wrote:
> Once that's done, it makes it easier to implement a better "bump" command --
> one that can use any published checksums and compute the rest, and warn if no
> checksums were published.
> https://trac.macports.org/ticket/53851
Sorry, this one is of
It's been pointed out before than when updating a port to a new version, one
should not just update the version and checksums in the portfile; one should
also verify at least one of those checksums with the ones published by the
developers -- assuming the developers publish them.
It would be gr
