On Tue, Mar 02, 2021 at 09:16:46AM +0100, Filippo Rusconi wrote: > > The brute force approach works for me: > > 1. install seqan-dev from buster (for step 2) > > 2. cp -a /usr/include/seqan debian/ > > 3. in debian/control remove the seqan-dev build dependency > > 4. in debian/rules pass -DSEQAN_INCLUDE_DIR=$(DEBIAN_DIR) > > to dh_auto_configure > > I first tried to check if putting some header files in the local source tree > would do. But no, in fact the file handling-related headers pull down almost > all > the seqan headers, so this strategy did not work out, leading me to envision > exactly what you tried.
Sorry, I'm reading your mail a bit late ... > I now wonder where to put the seqan headers when we > install the -dev stuff, so that people working with OpenMS do find them. I > thought creating a seqan subdirectory to the /usr/include/OpenMS directory and > point the compiler to that location by providing -I/usr/include/OpenMS. > > But then, how do we inform the users about the unconventional location of the > header files? Do they actually need that location ? > > Any idea ? I took the freedom to strip down the headers to those that are really needed to build the package. Well, its 8MB extra load - but for this package its "only about 1%". Not nice definitely, but given the fact that we probably will not have the time for a better solution I simply uploaded to meet the freeze deadline. The extra files are documented in debian/README.source and I hope for Debian 11 we will find a better solution. Hope this helps solving the hassle we created by removing seqan-dev package. Kind regards Andreas. -- http://fam-tille.de