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

Packaging devel-only C++ library


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

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?) ?


GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini <enrico@enricozini.org>

Attachment: signature.asc
Description: PGP signature

Reply to: