[Bug 523540] Review Request: opentracker - Bit Torrent Tracker

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=523540


Matt Domsch <matt_domsch at dell.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |matt_domsch at dell.com




--- Comment #7 from Matt Domsch <matt_domsch at dell.com>  2009-10-15 22:59:02 EDT ---
opentracker isn't a library, it's an executable, and yes, it statically links
against libowfat (libowfat is only available in a static libraray).  So that
error can be ignored.  This situation is even recognized in the packaging
guidelines for statically-linked executables, so it doesn't require FESCo
approval.

This is configured as an open tracker, yes?  Meaning anyone can upload any
torrent to it.  For Fedora Infrastructure use, I wouldn't want to put into
production this kind of service - I would want to use the closed mode (which I
know, the authors abhore).

Furthermore, I'd really like to see a second build, enabling the IPv6-only
mode, be included.

It's too bad the upstream doesn't provide runtime config options for these two
features (open vs closed mode, IPv4-only vs IPv6-only).  What you find is that
you'd need 4 executables built to satisfy that matrix.

I've built libowfat for EL-5 today, linked against glibc and not dietlibc. 
I'll go ahead and commit that.  Then I ask you to create an EL-5 branch for
opentracker once your package here is approved.  For FI, I need IPv6-only,
closed tracker mode.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.