[PC-BSD Pbi-dev] All in one approach to modules

Eitan Adler lists at eitanadler.com
Tue Oct 4 12:14:53 PDT 2011


> pkg-plist files are generally not required for a port. They are used
> when there is a large number of files that need to be included, but
> there are many smaller programs that only have a few libraries/files and
> simply list them in the makefile under PLIST=(whatever). However, if a
> pkg-plist exists, I think it is a good idea to look for files in the
> */bin/ category.

The only way to obtain a complete and usable pkg-plist is to run
make generate-plist fix-plist-target && cat $(make -V TMPPLIST)

MAN, NOPORTDOCS, PLIST=, plist variable substitution, etc all cause
different plists to be generated.

> The only issue with *requiring* a port to put something in the
> PREFIX/bin/ directory is that some server applications don't have
> binaries in */bin/ because everything is contained in */etc/

Some programs write to sbin/ as well.

-- 
Eitan Adler


More information about the Pbi-dev mailing list