Hi Jonas, Вт 28 апр 2020 @ 10:09 Jonas Smedegaard <d...@jones.dk>:
> The package swi-prolog-nox is described as a compiler for the language, > and the package depends on packages containing development headers. > > That's fine for a _development_ environment, but not ideal in general. > > I maintain the package eye, which is _implemented_ in Prolog, > but need only the ability to execute a set of existing Prolog code, > without a need to compile any new Prolog code. > > It would be better if possible for eye to depend on a package for > executing its Prolog code without also pulling in development packages. > > Thanks for considering, Thanks for your bug report! As for swi-prolog in Debian I plan to provide more small packages instead of packaging almost everything into swi-prolog-nox. As upstream migrated to cmake it is not difficult now, but still requires some time. Currently I'm thinking about providing swi-prolog-core (with Core_system component, which means compiler and core libraries) and swi-prolog-core-packages (with Core_packages component, which means packages with few dependencies). I'm not sure which features are required for the eye package. If it if just Core_system, then (if I'm correct) it will not require development packages except libgmp-dev. But I need some free time for working on it. It is possible to break swi-prolog-nox into more packages (say, one package per cmake component), but currently we lack a tool to calculate dependencies between swi-prolog packages (which I see as a dh tool, say dh-swi-prolog or something, like we have for other languages). Developing such tool also requires some time investments. Cheers! Lev
