On Tue, Aug 22, 2017 at 05:26:50AM +0100, Stuart Henderson wrote: > It doesn't work with a simple update from an old installation (after > updating, there's no output from "r2e run" or "r2e list"). That's why it > hasn't been updated before, btw. > > There's a proper uploaded distfile on pypi which is generally preferable > to a github autogenerated tar file (MODPY_PI=Yes). > > NO_BUILD should be removed. There are tests now which coukd be enabled, > though I'm not sure if they're actually useful.
I agree that this port can't be updated as-is because it breaks with no easy way to fix (no v2 -> v3 config conversion tool or something). What is the usual course of action? Make a new port rss2email3? In any case, as Sebastien Marie points out, upstream will move once again very soon (in a matter of days). Looking at the forks @jsbackus (the guy from the GitHub issue) wants to merge, there are a *lot* of changes there. And since this is a new fork, they might take this opportunity to make one-off super breaking changes. I will put this port on the shelf for now until the new upstream coalesces and makes all of the breaking changes they want. Then I'll submit an entirely new port. They might change the name, too, since there are now 2 rss2email upstreams, both dead, floating around. -- Kaashif Hymabaccus GPG: 3E810B04
