Hi ports@, Here is the new release of rss2email. As before, it is a new port and not an update of rss2email since it is completely incompatible and I don't want to break users' perfectly fine configurations.
Some concerns from last time have been addressed: Q: Is the new upstream (https://github.com/rss2email/rss2email) the canonical upstream? A: Yes, the old maintainer W. Trevor King has added the new maintainers to the PyPI package (https://pypi.org/project/rss2email/) and this is where we have released 3.10. Q: Why is "3" embedded in the port name? What happens when version 4 is released? A: As one of the maintainers of the project, I can personally guarantee version 4 will never be released. We will never break compatibility (big statement I know) and there will never be a major version bump. If there are better naming ideas, I am open to them. Q: Why would I use this instead of my already working rss2email-2.71 setup? A: We got all of the people who had forked rss2email under one roof and collected all of their previously bugfixes and new features. Like support for writing to maildir, working tests, some SSL fixes, some feed parsing fixes, etc. I think it works better than 3.9 (which is actually not even in ports, so maybe this is irrelevant). And not to mention, this is the only version with active maintainers who will respond to problems. Q: Does it work on the undeadly.org RSS feed? A: Yes! Or at least it does on my machine. The only issue I have is that "make test" hangs but if you manually go to WRKSRC and run the tests it works. Probably something to do with the fact the tests start a web server? I am really keen to get this in eventually since I've been using it for an extremely long time. Testing and suggestions are very welcome. -- Kaashif Hymabaccus GPG: 3E810B04
rss2email3.tgz
Description: Binary data
