From Newsgroup: muc.lists.freebsd.ports

Hi,

Can DOCS include MANPAGES?
I'd like to build my ports with just manpages and examples.
Does disabling DOCS globally also clobber ports manpages?
--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Thu, Aug 28, 2025 at 9:22rC>PM void <void@f-m.fm> wrote:

Hi,

Can DOCS include MANPAGES?
I'd like to build my ports with just manpages and examples.
Does disabling DOCS globally also clobber ports manpages?

I'm not a portmgr, so this is all my humble opinion:
Ideally we should strive to separate DOCS and MANPAGES. But sometimes
the software's buildsystem has a single "docs" switch that controls
both manpages and html/pdf/etc. generation. In this case I don't go as
far as decoupling DOCS and MANPAGES and stick with only DOCS.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Thu, Aug 28, 2025 at 09:37:21PM +0300, Gleb Popov wrote:

I'm not a portmgr, so this is all my humble opinion:
Ideally we should strive to separate DOCS and MANPAGES. But sometimes
the software's buildsystem has a single "docs" switch that controls
both manpages and html/pdf/etc. generation. In this case I don't go as
far as decoupling DOCS and MANPAGES and stick with only DOCS.

OK, thanks.

I guess there's not an official way of processing the ports tree to
see what's where? There's a couple of issues, might be near-edge cases,
in that on a for example embedded system one might not want doxygen
or PDFs made. I install docs-everything in a desktop context,
manpages only elsewhere.
--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Thu, Aug 28, 2025 at 9:56rC>PM Derek Schrock
<dereks@lifeofadishwasher.com> wrote:

sub-packages solve this for all cases. You might still have to build
them but they get their own package.

Not really, subpackages is a way to get multiple packages from a
single build (read, ${WRKDIR}).
The question is about OPTIONS, which are inputs to the build (the
build recipe actually).
In other words, OPTIONS allows for not building some part of the
software at all, saving the
time on build dependencies, while subpackages allow for more
fine-grained installation of
build products on the end point.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports

On Thu, Aug 28, 2025 at 9:59rC>PM void <void@f-m.fm> wrote:

OK, thanks.

I guess there's not an official way of processing the ports tree to
see what's where? There's a couple of issues, might be near-edge cases,
in that on a for example embedded system one might not want doxygen
or PDFs made. I install docs-everything in a desktop context,
manpages only elsewhere.

Yes, I saw such decoupling as well. For instance, if docs generation
requires Doxygen,
which is a pretty heavy build dep, the port does something like this: OPTIONS_DEFINE= DOCS DOXYGEN
DOXYGEN_IMPLIES= DOCS
DOXYGEN_BUILD_DEPENDS= doxygen:devel/doxygen
DOXYGEN_CMAKE_ON= BUILD_DOCS
This allows for users to disable the DOXYGEN option by default, but
enable DOCS and MANPAGES,
and then hope for a better port building experience.
Another example of the same idea is lang/ghc with DOCS and PDFDOCS.
--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.ports


--l534fgx5sls2vuxc
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 28, 2025 at 07:22:10PM +0100, void wrote:

Hi,
=20
Can DOCS include MANPAGES?
I'd like to build my ports with just manpages and examples.
Does disabling DOCS globally also clobber ports manpages?

So, the answer is no, a port's man pages should not be hidden inside
DOCS, if a port needs to add an option for man pages, because, for
example, they need to be generated with some tool, it should be behind a MANPAGES option, and that option should be enabled by default.
There are propably ports that go against that paradigm, and they should probably be reported and fixed.

--=20
Mathieu Arnold

--l534fgx5sls2vuxc
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQITBAABCgB9FiEE9XJBpJetWizkEBUef2IOCp6dQb4FAmi/vUZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEY1 NzI0MUE0OTdBRDVBMkNFNDEwMTUxRTdGNjIwRTBBOUU5RDQxQkUACgkQf2IOCp6d Qb6kbgwAleRh29bu8sEFgpT21lxP5bBnBAWTMACTKCqoKeOx2p60DijXqKQGvzcO YkvTYT1MR2V3zos4kX4uLyNYA8GA75uWVOF75nhk0ZC19KNzu1DZLyop9yQbWFmG r+2EdjgzVlW4T7BaPpZoGYee/9CjpOutc3il4CU3TCbcQVO1FpbSRhCLJT+c4zYu qTEU9/3QqcO+jY9h9EQIcRvaJh4d6yO4aSYS6AOmdIh9+EsemcvOmby9R8KMFoWM Rot01bI2YF3CwL0dlNkdRoZfs92lZHHuRhCSk34Y6KmSrPqJ/GRWxc6lg/bqCkYI rmWsyhqx9A6CxdMQz+zppVJr92CfNgeSY7lYFJjGxfnXAqCFvdpNvTqoRKaWC4DB sNEB77F3ZorgywKUzZO0/RHPCvtOBk8n/NesSrQWJ9c/ZFWIqEjVmaWKqpjr/3q9 pO/nLHB5hd1Wiq3SB5IdQpFfnwIH65FbgG4BGzT8xZqnNG4e5LNvOCYuT6tktcc8
aqhCeKne
=x0uD
-----END PGP SIGNATURE-----

--l534fgx5sls2vuxc--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21a-Linux NewsLink 1.2