10 replies to this topic

[malakudi]

I would like to try implement building the transmission torrent client daemon in openembedded (in order to get more familiar with bitbake and also deliver this very usefull torrent client on our boxes). source package is using common "configure ; make ; make install" procedure. Is there a simple "getting started" kind guide to converting such a package into openembedded?

[MiLo]

Yes, on openembedded.org there's a simple description.

[malakudi]

It seems transmission already exists in openembedded used by OpenPLI (though a bit older version). I managed to built it (first I had to build curl). Can you add it on the list of supported packages for images so that it will be available for downloading with opkg on OpenPLI 2.0 beta?

I will now try to adapt already existing transmission_1.91.bb for the latest version (2.13)

[MiLo]

I think that would be possible. There's also "ctorrent" in the feed, which appears to do the very same thing, so in what respect is transmission a better choice?

[malakudi]

transmission has a very comfortable web contol interface (on port 9091), it is the most used torrent client in embedded devices (NMTs, NAS, routers etc). It is also very actively developed, it is always up to date with bittorrent protocol updates (DHT, PEX, Magnet Link etc). ctorrent is not actively developed, doesn't have a contol UI and I would consider it obsolete.

[xener]

have you ever heard about CTCS?
obsolete is a big word, there are many protocols/applications which are not developed for long time, but are used at present days , many times instead of newer protocols/applications.
but i understand you, some peoples, without buttons, icons and mouse feel lost ;-)

[malakudi]

have you ever heard about CTCS?
obsolete is a big word, there are many protocols/applications which are not developed for long time, but are used at present days , many times instead of newer protocols/applications.
but i understand you, some peoples, without buttons, icons and mouse feel lost ;-)

I know ctcs. I called it obsolete because:
1. it hasn't seen any code development since 15/06/2008
2. it doesn't support magnet links and other improvements.

for console based torrent client I prefer rtorrent (curses interface). But for embedded, transmission is far more suitable. Anyway, anyone can use whichever he/she likes.

[MiLo]

I will now try to adapt already existing transmission_1.91.bb for the latest version (2.13)

And?

[malakudi]

I will now try to adapt already existing transmission_1.91.bb for the latest version (2.13)

And?

I've adapted openwrt's bitbake rules for latest transmission package to openpli, I'll upload them as soon as I finish some improvements in the v4l-dvb bitbake rules. I am including some patches from sifteam's openee (open extreme edition) which, among others, support tda18218 demodulator needed for many AF9015 chipsets.

[MiLo]

I've already built a transmission 2.13 recipe in the openPLi feed which appears to work, I'd suggest building on that instead of starting from scratch...

[Taykun345]

malakudi, we are waiting for volar a850 support