actually follow the links, and change references from DigiBoard
to Digi International (I'm currently working for Digi, and we were
just asked to do the same thing with everything we are working
on when possible, so I figured I might as well do the same under FreeBSD).
Fixed DPADD again.
mk/bsd.README
Don't list the LIBXXX identifiers here. Describe them better.
mk/bsd.prog.mk
Updated the list of LIBXXX identifiers.
- recently added library libdisk.a wasn't mentioned (required for sysinstall)
- old objects kz*.o weren't mentioned
- old libraries libc_pic.a, libcom_err.a, libf2c.a, libg++.a, libgcc_pic.a,
libgmp.a, libipx.a, libkeycap.a, libss.a and libxpg4.a weren't mentioned
- old libraries libgnumalloc.a and libftp.a no longer exist
- old library libmp.a was said to not exist
- deprecated links libfl.a and libln.a weren't mentioned
"foo", what this does is:
(1) Put all distfiles and patchfiles in /usr/ports/distfiles/foo
(2) Go to ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/foo when the
master site is down
When your port has a lot of dist/patchfiles, or has a file that does
not have a very port-specific name (e.g., "Makefile"), set this
variable instead of redefining DISTDIR. (If you redefine DISTDIR, (1)
will work but (2) will not.)
Agreed that it's a good idea by: adam
since I've no idea what the ISO standard for Italian keyboards is, but we
can always adjust it later and this is better than the nothing we had before.
Submitted by: Gianmarco Giovannelli <gmarco@masternet.it>
port documentation (which can be things like postscript manuals
describing every single of the 65,536 options) from being installed
into ${PREFIX}/share/doc.
(Sorry Jordan, but your other idea (${CATEGORIES}) was a major hit.)
Also remove the keyword field in the INDEX line and replace it with
two columns: build-time dependencies and run-time dependencies. They
are both list of package names (minus the ".tgz").
(1) people can have weird paths and it will still work, and
(2) if you really need to use /usr/local/bin/cp instead of /bin/cp,
you can do that by changing only one line.
Submitted by: wosch
Ideally, this should go into the ``mail'' section of the handbook, but
i don't have the time to write all of this right now, so i've put it
into the FAQ.
so that the developer section isn't garbaged up.
Suggestion: anytime you mess with the handbook, build it
and actually look at the result with your favorite browser, since
a one character typo can mess up the whole thing.
