I'm working on packaging stan, which has an unusual structure. stanc, a binary, is the stan compiler. It converts stan code to C++, which it then hands to the C++ compiler. The user writes the stan code and then runs the resultant binary.
As a result of this, files like headers and (probably) libraries that would ordinarily go in a -dev package are actually needed by a user who is not interested in building the original system (stanc and friends). It seems there are at least two choices: 1) Retain the -dev package for stuff associated with compiling tirggered by the user, and declare a dependency (as well as a build-dependency) of the regular stan (or rstan) package on the -dev package. 2) Don't have a -dev package and either include the necessary materials in the main package or perhaps put them in a -common package. (-common because there is a free-standing stan and a version designed to be called from R). Note that the headers are also necessary when building stanc from source. Any advice? Ross Boylan -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1377796060.3875.44.camel@localhost