Date: Mon, 23 Nov 2009 12:21:18 +0000 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: David Fries <djf@gmx.ch> Cc: freebsd-ports@freebsd.org Subject: Re: Newbie question about additional documentation Message-ID: <4B0A7E3E.4020500@infracaninophile.co.uk> In-Reply-To: <20091123112929.151170@gmx.net> References: <20091123112929.151170@gmx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig697C68ADD12799A0CF9CBE6F
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
David Fries wrote:
> Hi everybody
>=20
> I started working on my first port (a Haskell cabal package) over the
> last weekend. I read the porter's handbook and then began by looking
> at similar ports that already existed in the ports collection (e.g.
> archivers/hs-zlib) to get a basic idea of what the port should look
> like. I noticed that the only documentation listed in pkg-plist of
> these ports is the LICENSE file. So pkg-plist looks something like
> this:
>=20
> ... other files..
> %%PORTDOCS%%%%DOCSDIR%%/LICENSE
> %%PORTDOCS%%@dirrm %%DOCSDIR%%
> ... @exec/@unexec...
>=20
> However, when you install the port (assuming NOPORTDOCS is not set),
> a HTML documentation will also be generated by the Haskell compiler
> and put into %%PORTDOCS%%%%DOCSDIR%%/html/*. So my question is, is it
> ok to omit these html files in the pkg-plist? I thought, you should
> list those too...
It's not OK to install files without any record in the pkgdb. If you do
things like that, firstly any committer working on the port should bounce=
it back to you as not fulfilling the required standards, and secondly, if=
the port does somehow get committed you'll be getting irate e-mails from
various QA systems that spend all their time looking for such problems.
Now, explicitly listing all of the files that get installed in pkg-plist
in the port directory is one way of dealing with this. There are alterna=
tives
though, which might suit your port better. Check out the PLIST_FILES and=
PORTDOCS variables in /usr/ports/Mk/bsd.port.mk -- in short these are:
PLIST_FILES a way of listing a short pkg_plist entirely from within
the port Makefile, which helps avoid using up inodes for
tiny little files
=20
PORTDOCS a way of automatically adding a whole directory tree of
documentation to the pkg pretty much automatically. This is
particularly useful if your docco is generated automatically
and you can't always know exactly what files there will be
beforehand.
Cheers,
Matthew
--=20
Dr Matthew J Seaman MA, D.Phil. Flat 3
7 Priory Courtyard
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW, UK
--------------enig697C68ADD12799A0CF9CBE6F
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.13 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAksKfkUACgkQ3jDkPpsZ+VZVWQCcDYa2xS/gKCLckrjB0Aetuw+0
X9oAn1xCnbnQsL4PKbQ9DmODyAwbCH2p
=CzfK
-----END PGP SIGNATURE-----
--------------enig697C68ADD12799A0CF9CBE6F--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4B0A7E3E.4020500>