On Thu, Jan 05, 2023 at 04:05:29PM +0100, Santiago Vila wrote: > Thanks a lot for the patch. > > Yes, it would make sense to move *.h and .a to a libdialog-dev package. > > But I'm not sure about the best way to proceed after reading the reply from > Thomas: > > > actually, a shared library is generally preferred for development packages. > > This is what I build for my own use (scripts in the package/debian > > directory), > > as "cdialog-dev": > > > > /usr/bin/cdialog-config* > > /usr/include/cdialog/dlg_colors.h > > /usr/include/cdialog/dlg_config.h > > /usr/include/cdialog/dlg_keys.h > > /usr/include/cdialog.h > > /usr/share/doc/cdialog-dev/changelog.Debian.gz > > /usr/share/doc/cdialog-dev/changelog.gz > > /usr/share/doc/cdialog-dev/copyright > > /usr/share/man/man3/cdialog.3.gz > > /lib/x86_64-linux-gnu/libcdialog.so@ > > In Debian the static library has always been named libdialog.a, > but the library according to the author is called libcdialog.so.
A development package could have both static and dynamic libraries. dialog can build either, but not both at the same time (just like ncurses). > If I go ahead and create a shared library package (which I suspect is > the only thing ftpmasters will accept if they see NEW binary packages), > should I worry about binary compatibility with other distros? > > Thanks. > -- Thomas E. Dickey <dic...@invisible-island.net> https://invisible-island.net
signature.asc
Description: PGP signature
