Thread: Transmission (Torrent client for 2008 OS)
View Single Post
Serge is offline Serge
2007-12-07 , 21:38
Posts: 503 | Thanked: 267 times | Joined on Jul 2006 @ Helsinki
#46
Originally Posted by pipeline View Post
The bora build is giving issues with platform.c @ the include /usr/include/pthread.h (around 12 identical errors of :
error: systax error before '*' token

Those lines (441, 446, 449, etc..) all seem to point to compiler not understanding the pthread_rwlock_t type.
This problem has been already fixed in Transmission SVN: http://transmission.m0k.org/trac/ticket/534

Regarding availability of sources, sure. I probably would have checked into garage svn the source once things settled a bit. And the deb can be reverse engineered with linux archiver and repackaged with pypackager. Was this request something you are interested in personally (perhaps you have plans?) or just ensuring good 'citizenship' ? If you have plans for this, let me know what you need.
Well, having everything available as open source is at the very least a good tradition and a sign of respect to all the work already done to bring this nice torrent client to maemo (the Transmission torrent client itself and the libraries it depends on are all open source). Keeping the very last bit (the packaging stuff) as closed source does not make much sense

I think that reverse engineering it is the last thing one would do. Just taking 'debian' directory from the standard debian distribution and starting a new packaging effort might be a more natural step. But I hope we will not have any need to use this last option

Anyway, having a full set of files that were used to build packages is important if you want other people to take part in improving build system. Also building a package for OS2006 with native 'gregale' SDK might be interesting.

A patch against the standard upstream Transmission sources which adds all the needed packaging stuff would be the best option to distribute your changes. Also it would be very nice to have version numbers in sync with upstream versioning scheme to avoid confusion (maemo transmission packages can have just an extra number which identifies patchlevel appended to the upstream version number, you can see maemo mplayer packages as an example).