On 10/1/19 7:05 PM, Axel Braun wrote:
Hello,
I'm currently working on packaging Orthanc. This installation can be extended with plugins, e.g. for database-backends and viewers.
Those plugins require the sources of Orthanc to compile (beside some other specialities).
In order to keep things easy and consistent, I packed the sources of orthanc into orthanc-devel. So with BuildRequires: orthanc-devel in the plugins one should be fine.
Now this is objected by the maintainer of the targeted development repository, sources inside -devel are not allowed.
Adding the othanc source tarball to each plugin separately sounds a bad idea to me. High risk of inconsistency. Having a -src package build together with -devel isnt smart either - it just adds overhead.
Any other ideas how to solve this?
Does it actually need all the sources to compile? Generally if its C or C++ the header files and libraries are enough (although sometimes plugins are different) traditionally the -devel package should just contain the header files installed into /usr/include/orthanc -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org