Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 05 Apr 2008 21:36:24 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Steven Friedrich <FreeBSD@insightbb.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Documentation for port config options?
Message-ID:  <47F7E2C8.6080507@infracaninophile.co.uk>
In-Reply-To: <200804051609.30739.FreeBSD@insightbb.com>
References:  <200804051609.30739.FreeBSD@insightbb.com>

next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig0EC17850A25395D3128B0F97
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Steven Friedrich wrote:
> cups-base has several options:
>=20
>  [X] GNUTLS    Build with GNUTLS library
>  [ ] PHP       Build PHP support
>  [ ] PYTHON    Build PYTHON support
>  [ ] LIBPAPER  Build with libpaper support
>  [ ] DNSSD     Build with DNS_SD (avahi) support
>  [ ] PAM       Build with PAM support
>  [ ] LDAP      Build with LDAP support
>  [ ] DBUS      Build with DBUS support
>=20
> Where can I find documentation regarding these options, so I can determ=
ine=20
> which ones I need?

That's actually a pretty hard thing to do, given the current way the
ports tree operates.  If you're lucky the port maintainer will have
commented the ports' Makefile nicely for you.  Another good place to
look is the documentation included in the source tarball of whatever
it is you are trying to build.  In that case, it helps if you can
follow through the logic in the ports Makefile to see what it does
to change the build when the option is toggled -- usually it's by
tweaking the options to  the configure script in the package sources.
Other possibilities are searching the web or asking someone knowledgeable=
=2E

Unfortunately there isn't a sure-fire way of getting any sort of
reasonable explanation of how port options work.  There is a proposal
being discussed over on the freebsd-ports@ list about adding a one
line explanatory snippet for each option, which would actually make
a pretty big difference despite the limited space to work with.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                   7 Priory Courtyard
                                                  Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey     Ramsgate
                                                  Kent, CT11 9PW


--------------enig0EC17850A25395D3128B0F97
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkf34s0ACgkQ8Mjk52CukIw5wgCfUtwzk1rR0ubaM3zUqjmWLoiC
Qn8AnRM0cSUrgZ32PA3onry5nVFeg6C7
=65y2
-----END PGP SIGNATURE-----

--------------enig0EC17850A25395D3128B0F97--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47F7E2C8.6080507>