freebsd-skq

History

Enji Cooper 7d9ade5da1 Integrate indent tests added in r313544 into ATF/Kyua and the FreeBSD test suite This change does the following: - Introduces symmetry in the test inputs/outputs by adding the exit code to the files. This simplified the test driver notably by requiring less filename/test name manipulation. - Adds a test driver for the testcases added in r313544, patterned after bin/sh/tests/functional_test.sh . The driver calls indent as noted in r313544, with an exception: The $FreeBSD$ RCS keyword's expansion is reindented with indent, which means that the output differs from the expected output. Thus, all lines with $FreeBSD$ in them are deleted on the fly, both in the input file and the output file. The test inputs/outputs are copied to the kyua sandbox before the test is run as the pathing in some of the files relies on pathing normalized to the current directory (copying the files is the easiest way to resolve the issue). Approved by: pstef (maintainer) Reviewed by: pstef X-MFC with: r313544 Sponsored by: Dell EMC Isilon Differential Revision: https://reviews.freebsd.org/D9682		2017-03-03 20:15:22 +00:00
..
BSD.debug.dist	Merge ^/head r312309 through r312623.	2017-01-22 16:05:13 +00:00
BSD.groff.dist
BSD.include.dist	hyperv/vss: Add driver and tools for VSS	2016-11-15 02:36:12 +00:00
BSD.lib32.dist	Handle lib32 files during delete-old* when MK_LIB32=no.	2015-10-20 20:35:34 +00:00
BSD.libsoft.dist	Add libsoft to the tree, just like lib32.	2016-01-03 04:32:05 +00:00
BSD.release.dist
BSD.root.dist	syslogd(8): add an 'include' keyword	2016-11-01 01:41:24 +00:00
BSD.sendmail.dist
BSD.tests.dist	Integrate indent tests added in r313544 into ATF/Kyua and the FreeBSD	2017-03-03 20:15:22 +00:00
BSD.usr.dist	Adjust version numbers for the clang library directory.	2017-01-05 18:32:18 +00:00
BSD.var.dist	tabs -> spaces in etc/mtree	2017-01-05 02:47:56 +00:00
Makefile	Add libsoft to the tree, just like lib32.	2016-01-03 04:32:05 +00:00
README

README

$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/ *$//' >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 committed, as it 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.