port versus path dependency declaration

[Ryan Schmidt]

On May 11, 2018, at 22:17, Ryan Schmidt wrote:

> As for why a dependency on pep8 is being written in path:-style, I don't know. I don't see a py-pep8-devel port. I don't know if there is another port that provides the same files as py-pep8.

I should have checked the history before responding to this.

The other port that provided the same files as py-pep8 was py-pep8-157.

py-autopep8 was switched from pep8 to pep8-157 here:

https://github.com/macports/macports-ports/commit/d273106a7c585334d4a788ded7a0b5d0ee0e164c

And it and other ports were switched back to pep8 here:

https://github.com/macports/macports-ports/commit/b375e3de7d7864e6612f3528e3cb1f11bcfdc9be

pep8-157 became obsolete here:

https://github.com/macports/macports-ports/commit/d4216c136e4ec3b14969a0d59fabb48d1cfab30d

And was removed here:

https://github.com/macports/macports-ports/commit/a512f8ec7f9ad5d5add04158c3b4168349238b5f

So I guess this means that there is no longer a reason why a port should depend on pep8 via a path:-style dependency; a port:-style dependency would be fine.