I don't see why this has been resolved as wontfix. My points: I. There isn't an actual conflict between the packages. They can coexist and work fine on the same system. You can't have the library for a protocol to conflict with a server, just because the server doesn't support the protocol correctly or fully. The two aren't tied to each other, you might run fso-gpsd and gpsd, and connect to gpsd with libgps19, and to fso-gpsd through the D-Bus interface it offers. This works just fine, there is absolutely no conflict between the packages themselves.
Besides, they do work together just fine for me, I have a few points on this at the end, but I don't consider them that important. II. fso-gpsd is needed on Neo FreeRunner phones for the following reasons: 1. It manages the GPS power correctly. Modifying the desktop files is not something I'm looking forward to, since I don't like the idea that they will be replaced with my next update. Such a configuration is bound to failure. 2. It provides a D-Bus interface that some people use for scripting. 3. The GPS on this phone isn't working correctly for me with gpsd, it works just fine with fso-gpsd. The problem is that I wait a whole lot until I get a fix. I would have no issue if fso-gpsd wasn't uninstalled by libgps19 for no reason. If fso-gpsd is removed from Debian because it sucks, that's fine, but this conflict is artificial. The package should either be removed completely, or it shouldn't be in a conflict. And about the gpsd compatibility. gpsd is meant to work over a network, and I have used it like that a lot. Which means that the protocol is more or less network protocol, and it should survive a slight difference between the library and the client. A change in the protocol is therefore an issue whether fso- gpsd exists or not, and you can't add conflicts with packages on other systems to avoid the breakage. You can also use a network server that is just as limited and "broken" as fso-gpsd is. You can't resolve this with a conflict either. fso-gpsd and libgps19 work fine together at the moment, I don't know whether this is by accident or not. fso-gpsd might be broken, but it can be used with this library. A future change in the protocol which might break it might also break network access. If this happens, fso-gpsd would have to be fixed just like the older network machines would have to be upgraded. Placing arbitrary conflicts would do little good. Also, even with a flaky support for the protocol, a server can still be used. I don't know it's not great, but we're all doing it. Maybe libxml2 should have a conflict with Internet Explorer? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
