[aur-general] AUR cleanup package list

[Xavier]

On Tue, May 27, 2008 at 1:52 PM, Allan McRae <mcrae_allan at hotmail.com> wrote:
>
> librtorrent - package in community?
> rs_rtorrent - package in community?
>

First comment on AUR :
Current version of rakshasa`s libTorrrent library modifyied not to
conflict with rb_libtorrent.

from http://libtorrent.rakshasa.no/ :
<<Disclaimer : This is not the same libtorrent project as the one
found on SourceForge. >>
Also this :
http://libtorrent.rakshasa.no/ticket/854

rasterbar project is there :
http://www.rasterbar.com/products/libtorrent/
http://sourceforge.net/projects/libtorrent

That situation is so stupid but how to deal with it?
Personally, I use only rtorrent + libtorrent which are great, and I
like to use them as distributed by upstream, without ugly hacks for
renaming libtorrent to librtorrent.
On the other hand, rakshasa libtorrent is apparently only used by
rtorrent, while rasterbar libtorrent is used by many clients :
http://www.rasterbar.com/products/libtorrent/projects.html

So if you want to use both in the same time, it makes more sense to
rename rakshasa one.

However, Arch is supposed to follow upstream, so Arch should consider
this is not its issue and let upstreams resolve it. In the meantime
(forever?), the users simply have to make their mind between both. No
need to have a thousand torrent clients installed in the same time.