[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#685575: opentracker ipv4 vs ipv6 package names

On 2014-08-31 10:30:24, Roman Valls Guimera wrote:
> As far as I can see, ipv6/ipv4 compatibility is configured at compile-time and it’s mutually exclusive. Therefore other distros created packages for each option:
> http://www.rpmfind.net/linux/rpm2html/search.php?query=opentracker-ipv4
> Obviously for the time being it would be advisable to do the same, unless someone wants to introduce the necessary C changes/configuration to detect ipv4/ipv6 on runtime.

Well that's dumb. :) I am not sure how would would make that work in the
debian package, short of compiling it twice, which also seems dumb, only
less so.

Full IPv6 support was a goal in *squeeze*, so i would feel kind of bad
introducing a package without it at this point. Also, from what I
remember, it's pretty easy to implement IPv6 support with backwards IPv4
compatibility - so it seems odd that the option disables ipv4. Maybe we
can talk with upstream?

There's a good example on how to setup an IPv6 daemon here:

Men often become what they believe themselves to be. If I believe I
cannot do something, it makes me incapable of doing it. But when I
believe I can, then I acquire the ability to do it even if I didn't
have it in the beginning.
                         - Mahatma Gandhi

Attachment: pgp6kQN1UC1Pc.pgp
Description: PGP signature

Reply to: