On 27.05.20 21:16, Enrico Zini wrote: > Hello, > > I'd like to package a new version of https://github.com/ARPA-SIMC/meteosatlib, > for which I'm upstram, which depends on the recently freed > https://gitlab.eumetsat.int/open-source/PublicDecompWT > > PublicDecompWT is a C++ development-only library released by Eumetsat, > with functions needed to decompress MeteoSat images. Historically it has > had a relatively stable API, but no guarantees are made about an ABI as > far as I know, and to make matters worse ABI-wise, it's C++. > > These options come to my mind: > > - use git submodules and pull PublicDecompWT into meteosatlib, in a way > slightly more convenient to the current instructions of obtaining the > zipfile from eumetsat and putting it there > - package PublicDecompWT as a devel-only library in Debian, and > build-depend on it for meteosatlib. > > Suggestions? Other ideas? Special things to keep in mind in cases like > this (Built-Using?) ?
I'm not sure why you wouldn't want to package it as a separate library, apart from maybe this being more work. I think it doesn't hurt Debian to have one more package. OTOH clean modularization usually has very strong benefits, which would be an argument for packaging it separately. My 2 cents, *t
