I am actually using the libtorrent 1.2.x branch on Slackware-current with qBittorrent,
so is this just a wait for it moment on upgrading libtorrent-rasterbar until 15 releases
or is there something that specifically needs the 1.2 branch?
Sent: Monday, June 01, 2020 at 8:56 PM
From: "Donald Cooley" <chytr...@sdf.org>
To: "SlackBuilds.org Users List" <slackbuilds-users@slackbuilds.org>
Subject: [Slackbuilds-users] libtorrent-rasterbar-legacy and libtorrent-rasterbar
From: "Donald Cooley" <chytr...@sdf.org>
To: "SlackBuilds.org Users List" <slackbuilds-users@slackbuilds.org>
Subject: [Slackbuilds-users] libtorrent-rasterbar-legacy and libtorrent-rasterbar
There are a few SlackBuilds that depend on the older 1.1 branch of
libtorrent-rasterbar: qBittorrent, miro, and tribler.
Meanwhile there is a 1.2 branch that has been around on GitHub for some
time and there is also a release candidate for a 2.* branch of
libtorrent-rasterbar.
I've prepared a package I've named libtorrent-rasterbar-legacy which
would simply be the older 1.1* branch for qBittorrent, miro, and tribler.
I've also prepared a 1.2 branch I've named libtorrent-rasterbar. There
is already a SlackBuild with that name but it seems to make the most
sense to reuse that name for the more current library.
What I would like to happen is that these three SlackBuilds - miro,
qBittorrent, and Tribler would change their dependency from
libtorrent-rasterbar to libtorrent-rasterbar-legacy.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
libtorrent-rasterbar: qBittorrent, miro, and tribler.
Meanwhile there is a 1.2 branch that has been around on GitHub for some
time and there is also a release candidate for a 2.* branch of
libtorrent-rasterbar.
I've prepared a package I've named libtorrent-rasterbar-legacy which
would simply be the older 1.1* branch for qBittorrent, miro, and tribler.
I've also prepared a 1.2 branch I've named libtorrent-rasterbar. There
is already a SlackBuild with that name but it seems to make the most
sense to reuse that name for the more current library.
What I would like to happen is that these three SlackBuilds - miro,
qBittorrent, and Tribler would change their dependency from
libtorrent-rasterbar to libtorrent-rasterbar-legacy.
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
_______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
