Bug#824520: Just don't
Philippe Cerfon <philcerf@gmail.com> writes:
> Hey Salvo.
>
>
> Well I've seen that discussion and upstream seems to be pretty hostile
> against distributions (and apparently security as well). :-(
>
> On the other hand, Debian now unfortunately lacks subsurface packages
> (while other distros have them, or at least more well integrating
> repos). So people may simply use the questionable packages provided by
> upstream (which are for the average user only secured by worthless
> https), which in turn may again decrease security for people.
>
> As you've said, libdivecomputer is probably not the problem, while
> it's already packaged for Debian, that version seems to be used by at
> least no package.
>
> And marble and libgit2: isn't libgit only used locally for storing the
> logs? Marble is of course an issue. it would be very sad if one could
> not longer see the dive sites on the globe. But better than nothing at
> all.
> Do you think it's difficult to get subsurface working with the
> official marble libs?
>
AFAIU, the current subsurface does not require libmarble.
I have packaged subsurface for my own use, using system git2, and
without the googleearth support. The only embedded library is
libdivecomputer.
I haven't had time to look carefully at how far from policy compliant
the package is, but there's obviously a few problems yet. And I don't
have any idea how hard it is to get the googlearth plugin working; it's
not a priority for me.
My work in progress is at
https://salsa.debian.org/bremner/subsurface.git
For now, it works well enough for my needs. I'm happy to take merge
requests, and maybe consider uploading it to debian if it gets to a
decent state.
If you have dgit, devscripts and sbuild installed, you can build a
package with
git clone https://salsa.debian.org/bremner/subsurface.git
cd subsurface
git deborig
dgit sbuild
d
Reply to: