[macports-ports] 01/02: py-diff-match-patch: new port, version 20121119

[Ryan Schmidt]

On May 11, 2018, at 18:34, Zero King wrote:

> On Fri, May 11, 2018 at 12:07:38PM -0500, Ryan Schmidt wrote:
>> 
>> On May 10, 2018, at 20:37, Zero King wrote:
>> 
>>> Zero King (l2dy) pushed a commit to branch master
>>> in repository macports-ports.
>>> 
>>> 
>>> https://github.com/macports/macports-ports/commit/5836a5624ac40d04cb12a73c4ef219c377100a16
>>> 
>>> commit 5836a5624ac40d04cb12a73c4ef219c377100a16
>>> 
>>> Author: Zero King
>>> AuthorDate: Fri May 11 01:35:20 2018 +0000
>>> 
>>> 
>>>    py-diff-match-patch: new port, version 20121119
>>> 
>>> ---
>>> python/py-diff-match-patch/Portfile | 33 +++++++++++++++++++++++++++++++++
>>> 1 file changed, 33 insertions(+)
>>> 
>>> 
>>> diff --git a/python/py-diff-match-patch/Portfile b/python/py-diff-match-patch/Portfile
>>> new file mode 100644
>>> index 0000000..a7cc717
>>> --- /dev/null
>>> +++ b/python/py-diff-match-patch/Portfile
>> 
>> 
>>> +master_sites        https://files.pythonhosted.org/packages/22/82/46eaeab04805b4fac17630b59f30c4f2c8860988bcefd730ff4f1992908b
>> 
>> We don't want to use this style of URL, which needs to be updated every time the port's version is updated. Can the "pypi" fetch group be used instead?
> 
> I used pypi2port in macports-contrib,

Fixed: https://github.com/macports/macports-contrib/commit/aac8f1b1e2012cd5472f41e119a7e61435544e6d

> and this is an inactive package
> that is unlikely to get any update soon.

But we still want all portfiles to exemplify best practices. Novice developers often learn how to write portfiles by cribbing from other portfiles.