Готовые RPM-пакеты для libtorrent и rtorrent ( Ready-to-use libtorrent and rtorrent RPMs )

[GoogleCodeExporter]

(English version below)
-----------------------

Для пользователей RedHat Enterprise Linux (CentOS, Scientific 
Linux и
прочих производных от него) собраны уже 
готовые к использованию пакеты
xmlrpc-c, libtorrent и rtorrent (с поддержкой XML-RPC). Вам 
лишь нужно
скачать и поставить бинарные пакеты для 
вашей архитектуры (есть также
SRPM-ы для тех, кому хочется собрать бинарные 
пакеты самостоятельно). Все
это добро доступно здесь: http://fateyev.com/RPMS/RHEL5/

Libtorrent и rtorrent при установке требуют 
libsigc++/libsigc++-2.0, найти
их можно на RPMForge или DAG Repository: 
http://dag.wieers.com/rpm/packages/libsigc++/ 
http://dag.wieers.com/rpm/packages/libsigc++20/

Особо отмечу, что libtorrent собрана с 
поддержкой обновленной версии
xmlrpc-c (1.14.8) для совместимости с rutorrent, 
которой требуется xmlrpc-c
версии старше 1.11. Rtorrent статически собран с 
новым curl (7.19.4),
поскольку в RHEL используется старая версия, 
несовместимая с последним
rtorrent. Спасибо Ilyas R. Khasyanov за идею 
статического включения curl и
исходный пакет.

Для тех, кто желает самостоятельно собрать 
пакеты из SRPM-ов:
------------------------------------------------------------
xmlrcp-c при сборке требует cmake, найти его можно 
в EPEL5:
http://download.fedora.redhat.com/pub/epel/5/

libtorrent и rtorrent при сборке требуют 
devel-библиотеки
libsigc++/libsigc++-2.0, найти их можно на также на 
RPMForge или DAG
Repository (см. выше).

Все остальные зависимости для сборки есть 
в стандартных репозиториях.

-----------------------------------------------------------------------
Ready-to-use libtorrent and rtorrent RPMs

For those happy people who using RHEL (CentOS, Scientific Linux etc.
descendants) some time ago I've built "ready-to-go" xmlrpc-c, libtorrent
and rtorrent RPMs (sure, with XML-RPC support included). All you need is to
download and install those binary rpms for your pc achitecture (SRPMS is
also available if you prefer to do it yourself). Well, this stuff is
available here: http://fateyev.com/RPMS/RHEL5/

Libtorrent and rtorrent will require libsigc++/libsigc++-2.0 (they can be
found many ways, e.g. at RPMForge or DAG Repository):
http://dag.wieers.com/rpm/packages/libsigc++/ 
http://dag.wieers.com/rpm/packages/libsigc++20/

Moreover, the libtorrent library was built with support of modern xmlrpc-c
(1.14.8) especially better compatibility with rutorrent, that requires 1.11
version at least. Also, rtorrent was statically linked with curl 7.9.14,
because the newest rtorrent version isn't compatible with old curl that
currently comes with RHEL. Ilyas Khasyanov gives me that great idea (about
static linking) and provides such initial packages. Thanks, mate! 

For those nerds who wanna build from SRPMs:
--------------------------------------
The xmlrcp-c package requires cmake, you can find it in EPEL5 repo:
http://download.fedora.redhat.com/pub/epel/5/

Now you shouldn't be surprised with the fact that libtorrent and rtorrent
both require libsigc++/libsigc++-2.0 development libraries; you can find
they on RPMForge or so (see above).

As I though, any other dependencies are trivial and can be resolved through
your linux distrib's repository.

Original issue reported on code.google.com by dfateyev on 26 Aug 2009 at 2:36

[GoogleCodeExporter]

That wasn't "a defect" as marked by system ;-) but some kind of usable info (I 
believe).

Original comment by dfateyev on 26 Aug 2009 at 2:39

[GoogleCodeExporter]

Original comment by novik65 on 26 Aug 2009 at 2:45

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

this is why i prefer freebsd and the ports system.
on freebsd you just do this:
cd /usr/ports/net-p2p/rtorrent && make install clean
(or cd /usr/ports/net-p2p/rtorrent-devel && make install clean for 0.8.5)
it compiles from source for your system and handles all dependencies cleanly, 
if you
wish to compile with xmlrpc-c you just select it from the easy ncurses menu, 
just
like all other ports installs. 

Thanks for these links though, i have friends who still use linux, i've been 
able to
convert MOST of them but some will probably ALWAYS be linux heads =)

Original comment by Wonslung@gmail.com on 26 Aug 2009 at 3:55

[GoogleCodeExporter]

> it compiles from source for your system and handles all dependencies cleanly, 
if you
wish to compile with xmlrpc-c you just select it from the easy ncurses menu, 
just
like all other ports installs. 

That's not so hard in linux too, but there's some issues with rtorrent. It 
perfectly
compiles with *any* curl and xmlrpc-c version, but totally doesn't works with 
them
(!!) The situation looks pretty simply at first glance, but it doesn't. Go 
ahead; 
are you sure that the `freebsd port system` resolves correctly these conditions 
due
compilation: a) curl version installed on system must be > 7.18 (rtorrent
requirement), xmlrpc-c must be > 1.11 (rutorrent requirement). Moreover, the
libtorrent library doesn't compiles with xmlrpc-c > 1.11 because its api was 
changed,
so additional patch requred for latest xmlrpc-c compatibility. 

Original comment by dfateyev on 26 Aug 2009 at 4:45

[GoogleCodeExporter]

mine compiles flawlessly every time on freebsd.
I've never had a problem compiling it on linux either, it's just not as simple 
of a
process. 

Compiling on linux consists of making sure you have the dependencies correct,
compiling wth the proper flags and running ldconfig

compiling on freebsd consist of:
cd /usr/ports/net-p2p/rtorrent-devel && make install clean

Original comment by ultraflu...@gmail.com on 27 Aug 2009 at 2:21

[GoogleCodeExporter]

and, yes, the entire point i was making is on freebsd it DOES compile with the 
proper
dependencies and it DOES have the option to compile with xmlrpc-c checked as the
default option (which is an rtorrent option) and libtorrent has the option to 
compile
with kqueue based polling by default.

as far as i know, it used xmlrpc-c 1.18 on freebsd.

It's not hard to install on any system but FreeBSD is ideal.  For multiple 
reason.

FreeBSD handles load better, has a more robust network stack and let's not 
forget
jails and ZFS.  not only does it run at LOWER load most of the time but it works
better under HIGH load situations.  FreeBSD is by far my first choice for this 
sort
of thing.  The only os i think might give it a run for it's money soon is 
opensolaris.

Original comment by Wonslung@gmail.com on 27 Aug 2009 at 2:28

[GoogleCodeExporter]

Well guys I'm glad to hear that it working on freebsd out of box. Every os has 
it's
own advantages and lacks (I can't discuss it out there ;) hehe 

Original comment by dfateyev on 27 Aug 2009 at 4:40