1
0
mirror of https://git.FreeBSD.org/src.git synced 2024-12-29 12:03:03 +00:00
freebsd/etc/mtree
Colin Percival 6fb01948ee Add portsnap to the base system. This is a secure, easy to use,
fast, lightweight, and generally good way for users to keep their
ports trees up to date.

This is version 0.9.4 from the ports tree (sysutils/portsnap) with
the following changes:
1. The experimental pipelined http code is enabled.  No seatbelts
in -CURRENT. (^_^)
2. The working directory has moved from /usr/local/portsnap to
/var/db/portsnap (as discussed on -arch two days ago).
3. Portsnap now fetches a list of mirrors (distributed as DNS SRV
records) and selects one randomly.  This should help to avoid the
uneven loading which plagues the cvsup mirror network.
4. The license is now 2-clause BSD instead of 3-clause BSD.
5. Various incidental changes to make portsnap fit into the base
system's build mechanics.

X-MFC-After:    6.0-RELEASE
X-MFC-Before:   5.5-RELEASE
X-MFC-To:       RELENG_6, RELENG_5, ports
discussed on:   -arch and several other places
"yes please" from:      simon, remko, flz, Diane Bruce
thinks this is a great idea:    bsdimp
Hopes he didn't forget any files:       cperciva
2005-08-08 20:10:06 +00:00
..
BIND.chroot.dist Create a separate directory for dynamic zones which is owned by the bind 2004-11-04 05:24:29 +00:00
BIND.include.dist Seperate out the optional parts of the include tree that are 2004-09-27 08:16:29 +00:00
BSD.include.dist Forgot to add this change when commiting geli. 2005-07-28 00:53:47 +00:00
BSD.local.dist Back out "rw" locale addition for reason unknown to me (forced by portmgr) 2005-06-10 20:14:38 +00:00
BSD.release.dist Mention the path to the README file in the header comment. 2001-06-26 13:50:33 +00:00
BSD.root.dist Add /etc/security, into which the BSM audit configuration files will be 2005-05-30 20:51:13 +00:00
BSD.sendmail.dist Scheduled sweep using the README guidelines. 2003-11-29 18:22:01 +00:00
BSD.usr.dist New Ukrainian locale: uk_UA.CP1251. 2005-03-04 14:24:30 +00:00
BSD.var.dist Add portsnap to the base system. This is a secure, easy to use, 2005-08-08 20:10:06 +00:00
BSD.x11-4.dist Move couple of directories out of mtree and into their respective 2005-06-15 02:27:41 +00:00
BSD.x11.dist Reincarnate SETUID code in man(1), not compiled in by default. 2002-01-22 15:15:38 +00:00
Makefile Start the dreaded NOFOO -> NO_FOO conversion. 2004-12-21 08:47:35 +00:00
README Sigh, this README is not a shell script. 2002-05-18 12:37:19 +00:00

$FreeBSD$

Note: If you modify these files, please keep hier(7) updated!

These files are used to create empty file hierarchies for building the
system into.  Some notes about working with them are placed here to try
and keep them in good working order.

    a)  The files use 4 space indentation, and other than in the header
        comments, should not contain any tabs.  An indentation of 4 is
        preferable to the standard indentation of 8 because the indentation
        of levels in these files can become quite deep causing the line to
        overflow 80 characters.

        This also matches with the files generated when using the
        mtree -c option, which was implemented that way for the same reason.

    b)  Only directories should be listed here.

    c)  The listing should be kept in filename sorted order.

    d)  Sanity checking changes to these files can be done by following
        this procedure (the sed -e is ugly, but fixing mtree -c to
        not emit the trailing white space would be even uglier):

            mkdir /tmp/MTREE
            mtree -deU -f BSD.X.dist -p /tmp/MTREE
            mtree -cdin -k uname,gname,mode -p /tmp/MTREE | \
		sed -e 's/ *$//' | tail +5 >BSD.X.new
            diff -u BSD.X.dist BSD.X.new
            rm -r /tmp/MTREE

        Note that you will get some differences about /set lines,
        and uname= gname= on certain directory areas, mainly man page
        sections.  This is caused by mtree not having a look ahead
        mechanism for making better selections for these as it
        traverses the hierarchy.

        The BSD.X.new file should NOT be commited, will be missing the
        correct header, and important keywords like ``nochange''.  Simply
        use the diff for a sanity check to make sure things are in the
        correct order and correctly indented.

    e)  Further sanity checking of the system builds with DESTDIR=/someplace
        are more complicated, but can often catch missing entries in these
        files.  I tend to run this more complete sanity check shortly after
        the target date for a new release is announced.

        If you want details on it bug me about it via email to
        rgrimes@FreeBSD.org.