Hi Emilio,

we haven't forgotten you. We've worked hard and we've released v0.16
with the requested changes.

See: https://github.com/scanmem/scanmem/releases/tag/v0.16
See: https://github.com/sriemer/scanmem-debian

Now I'm asking you to upload the package. TIA

On 01.06.2016 23:14, Emilio Pozuelo Monfort wrote:
>> Lintian is only still warning about the fact that libscanmem is not
>> provided in a separate package. It is only there for better backend
>> communication for GameConqueror. So this can be ignored.
> 
> Hmm. If that's the case, you shouldn't install the libscanmem.so symlink. I 
> see
> you use it for dlopening the lib in gameconqueror, but that could happen by
> dlopening libscanmem.so.1. Also, it would be better if the library was 
> installed
> into a /usr/lib/scanmem/ directory (or similar) so it wasn't on the default
> library search path. Though I don't think that's strictly necessary.

We've addressed this like you've proposed. GC uses an absolute path to
libscanmem.so.1 as well now. The package libscanmem1 only installs
*.so.1 and *.so.1.0.0 to /usr/lib/scanmem/. The libscanmem-dev package
installs *.so and *.a.

> gameconqueror depends on scanmem (>= 0.15.7). What prevents scanmem from being
> upgraded to, say, 0.16, where libscanmem has changed incompatibly, while
> gameconqueror stays at 0.15.7? You should probably add a strict versioning.

The strict versioning has been added.

> Other than that things look good.
>  
> I'll upload as soon as those comments are addressed.

I've updated the "master", "source" and "testing-amd64" branches of the
scanmem-debian repo. These should contain everything to check that we've
done our job.

Lintian is happy. The packages work perfectly fine.

So we're ready to upload.

Please upload! TIA

Cheers,
Sebastian

Reply via email to