All cross reference labels start with name of the file that contains
them. A label for the top section level is simply the name of the
file (omitting the .sgml). Other references within the file append a
colon and onother name. For example, the label on the mailing list
section in the file eresources.sgml is eresources:mail. This gives
each file its own cross reference namespace.
ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/
as our distribution point for distfiles and patches. Other than
cosmetic changes (freebsd.cdrom.com -> ftp.freebsd.org), the
omission of "ports" is important. I would like to move this
directory completely out of the ports tree (on the ftp site),
so that people who do "get ports.tar.gz" won't get a bogus distfiles
-> ../distfiles symlink (which will make "make fetch" fail).
Sometime around the 2.1 release, the distfiles link will be deleted.
set permissions and ownerships of PREFIX (usually /usr/local). This
is the default if USE_IMAKE or USE_X11 is set.
This should be useful for machines like thud, where we want to keep
the /usr/local subtree writable to a group ("ports" in our case). Anybody
who installs stuff in /usr/local should have this set in the environment.
Note this won't affect anything the pkg_* suite does.
Note that the two "touch"s I took out from do-patch shouldn't have
been there in the first place.
This target may give incorrent results if two separate patches deal
with the same file, and their hunks overlap. (But having those kinds
of patches are bad, and they should be merged anyway.)
Reviewed by: hsu
arcihves of the mailing lists and usenet groups.
Renamed the last part "Appendicies"
Moved "PC hardware reference" to the Appendicies section and added
an introduction.
Fixed a dangling cross reference. (submitters.sgml)
".../packages/All". The "all" category that was automatically added
for every package is gone.
Note that bsd.port.mk requires category names to start with lowercase
names, otherwise it may get confused.
Reviewed by: jkh
By the way, here is a small script to convert your local package
hierarchy. Run it in bash, as /bin/sh not only will bark at the
$(.) command substitution but will also botch the [a-z]*/*.tgz
expansion (long-standing and annoying bug, reported before).
cd /usr/ports/packages
mv .packages All
for i in [a-z]*/*.tgz; do
j=$(basename $i)
/bin/rm $i
ln -s ../All/$j $i
done
Add Bt956 as being supported.
Include 2940 in the 2742/2842 section.
Anyone with a new feature or driver in 2.0.5 should think about adding "blurbs"
to this file. Some features say exactly what they do, others say nothing...
this document needs some rounding out.
The site in Island has only the 1.1-RELEASE dist.
The previous South Africa sites are dead and the brasilian one
is very hard to get into and painfully slow.
The two South Africa sites come from MIRROR.SITES.
2. Adjust some of my previous wording to be more indicative of the way things
currently are and using less bogus corporate categorizations ("Directors"
and "Officers" only exist in real corporations, which the FreeBSD Project
is not, so it sounded kind of pompus on reflection).
Rearranged a few sections, add memoryuse section.
current.sgml, ports.sgml, porting.sgml
Added a <label>s for cross reference targes.
submitters.sgml
Lots of editing, added cross references to other sections of
the handbook. Added a sample BSD-style copyright statement.
eresources.sgml
Updated the mailing list section, thanks to Peter Dufault.
authors.sgml
Added Peter Dufault, David Greenman and Joerg Wunsch.
memoryuse.sgml
A new section about how/where in PC memory the FreeBSD kernel
gets loaded and run.
one of the key components of the system, but I'm sure that this:
===
- ${ECHO_MSG} "===> Registering installation for ${PKGNAME}"; \
+ ${ECHO_MSG} "===> Registering installation for ${PKGNAME}"; \
===
change has absolutely no chance to screw us up, right? :)
Ports for which we can't build packages should define NO_PACKAGE but
still prepare pkg/* files. The user who really wants a package and
clear of the legal problems can say FORCE_PACKAGE from the command line
to build a package anyway.
package: check installation, build package, create links,
touch cookie
repackage: ditto but don't check cookie
package-noinstall: just build package from installed stuff, no cookies
involved at all
package-links create the symbolic links only
delete-package: delete package and symbolic links
delete-package-links: delete links only
These should make the management of the spaghetti of package links
a little friendlier. :)
