On Mon, 5 Jul 2021 17:15:09 -0400
"trondd" <tro...@kagu-tsuchi.com> wrote:

> On Mon, July 5, 2021 9:53 am, Charlene Wendling wrote:
> > Hi,
> >
> > The below diff updates snownews to 1.8 with a new repo owner and
> > finally a lot of modern features [0]! I tend to separate upstream vs
> > ports changes, but it's unpractical here:
> >
> >> Added Atom feed support
> >   Modify COMMENT and DESCR accordingly. While here, update to valid
> >   feeds and a mix of RSS and Atom. HTTPS is used where applicable.
> >> Use curl for networking
> >   Add proper LIB_DEPENDS, remove README now that HTTPS is supported.
> >   There is a year 2038 printf() warning, but it would require to
> >   sprinkle CURLINFO_FILETIME_T instead of CURLINFO_FILETIME in many
> >   places first. Also, refresh WANTLIB, and remove the netio.c patch
> >   accordingly.
> >> Use the OPML format to store the feed list, and XDG dirs
> >   Snownews-1.8 will migrate your urls file to the OPML format in
> >   ~/.config/snownews where you can find other settings (key
> > bindings, colors etc.). The OPML conversion tools (snow2opml,
> > opml2snow) have been removed, so we don't need p5-XML-LibXML as a
> > RUN_DEPENDS.
> >> Use UTF-8 everywhere (including manpages)
> >   The upstream configuration system couldn't find our ncurses
> > library with wide chars support, so i needed to tweak CFLAGS and
> > LDFLAGS.
> >> Deal with lack of verbosity for the fake stage
> >   The most painful part of that update has been the fake stage,
> >   because upstream hides issued commands, so i preferred to
> >   unsilence them.
> >
> > All the rest is mostly updating old patches.
> >
> > Testing:
> >
> > It builds and works fine on amd64 and macppc.
> >
> > Note that feed items' text enclosed in '<content type="xhtml">' is
> > not displayed (yet?).
> >
> > Comments and feedback are welcome,
> >
> > Charlène.
> >
> >
> > [0] https://github.com/msharov/snownews/releases
> >
> 
> Thanks.  I use snownews.  It converted my configs and works as
> epxected. I had to go back in and clean up all the calls to external
> conversion tools that the previous version needed but that's to be
> expected.  Worked either way.
> 
> Tim.
> 

You're welcome! I tried beforehand with a few feeds, but was not 100%
sure how the migration would really fare for current users. The commit
message will mention this, but given it works in either way it should be
smooth for everyone.

Charlène.

Reply via email to