On Mon, Jun 11, 2018 at 04:31:34AM -0300, Elias M. Mariani wrote: > Is not a problem, but lots of packages allready build py-package, > py3-package and if the default policy is to split the docs you will > have also py-package-docs. > Pro: > - Less size of the port when you dont need the documentation, if you > add to the number py-packages required for several packages this would > be pretty good! > Con: > - 3 packages instead of 2. > - A little more complexity in the Makefile to make docs only for one flavor.
Well, just have both main packages depend on the doc subpackage, and the end user, which is all that matter, shouldn't see the difference. The docs subpackage won't even show up on pkg_info -m. But, basically, the subpackage addition more or less amounts to: MULTI_PACKAGES = -main -doc RUN_DEPENDS-main += databases/py-sqlalchemy,-doc FULLPKGNAME-doc = py-sqlalchemy-docs... FULLPKGPATH-doc = databases/py-sqlalchemy in the Makefile. and you would also need to tell doc that it's conflicting with both older packages. It's really not that complicated. Thanks to landry, we fixed the last bug regarding those things in qwt.
