d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
6d7c1bdccd
freebsd-dev/usr.sbin/config/configvers.h

46 lines
1.8 KiB
C
Raw Normal View History

Recognize a %VERSREQ=nnnnn string in the system Makefile. Both config(8) and the kernel will have a 'config interface version number'. If an incompatable change is made to the kernel that requires a rebuild of config(8) (such as the cam devtab stuff), then the version number would be bumped in both places. If a user neglects to rebuild config, then they will get a nagging (but non-fatal) warning that they need to rebuild config.
1997-10-22 00:38:48 +00:00
/*
* 6 digits of version. The most significant are branch indicators
Make config(8) understand ORed dependecies in "files*" and improve tracking of known devices. Bump config(8) version.
2005-11-27 21:41:58 +00:00
* (eg: RELENG_2_2 = 22, -current presently = 70 etc). The least
Add some rationale about when to bump and not bump the config version. Clarify that it is not like the shlib versions, and not like param.h's __FreeBSD_version/osreldate either. When config(8) was actively changing a while back, the interface between config and the build system (eg: /sys/conf/files.* and Makefile.*) was changing rapidly. configvers is a version number of that interface. User specified config files do not have a version number. The decision about whether a user supplied config file is syntactically valid or not belongs to the parser and sanity checks, not an arbitary number.
2005-11-07 17:37:27 +00:00
* significant digits are incremented as needed.
Recognize a %VERSREQ=nnnnn string in the system Makefile. Both config(8) and the kernel will have a 'config interface version number'. If an incompatable change is made to the kernel that requires a rebuild of config(8) (such as the cam devtab stuff), then the version number would be bumped in both places. If a user neglects to rebuild config, then they will get a nagging (but non-fatal) warning that they need to rebuild config.
1997-10-22 00:38:48 +00:00
*
Add some rationale about when to bump and not bump the config version. Clarify that it is not like the shlib versions, and not like param.h's __FreeBSD_version/osreldate either. When config(8) was actively changing a while back, the interface between config and the build system (eg: /sys/conf/files.* and Makefile.*) was changing rapidly. configvers is a version number of that interface. User specified config files do not have a version number. The decision about whether a user supplied config file is syntactically valid or not belongs to the parser and sanity checks, not an arbitary number.
2005-11-07 17:37:27 +00:00
* DO NOT CASUALLY BUMP THIS NUMBER! The rules are not the same as shared
* libs or param.h/osreldate.
*
* It is the version number of the protocol between config(8) and the
Minor comment tweak to prevent gcc from being upset about the substring /* appearing in a comment.
2005-11-07 18:45:46 +00:00
* sys/conf/ Makefiles (the kernel build system).
Add some rationale about when to bump and not bump the config version. Clarify that it is not like the shlib versions, and not like param.h's __FreeBSD_version/osreldate either. When config(8) was actively changing a while back, the interface between config and the build system (eg: /sys/conf/files.* and Makefile.*) was changing rapidly. configvers is a version number of that interface. User specified config files do not have a version number. The decision about whether a user supplied config file is syntactically valid or not belongs to the parser and sanity checks, not an arbitary number.
2005-11-07 17:37:27 +00:00
*
* It is now also used to trap certain problems that the syntax parser cannot
* detect.
*
* Unfortunately, there is no version number for user supplied config files.
*
* Once, config(8) used to silently report errors and continue anyway. This
* was a huge problem for 'make buildkernel' which was run with the installed
* /usr/sbin/config, not a cross built one. We started bumping the version
* number as a way to trap cases where the previous installworld was not
* compatable with the new buildkernel. The buildtools phase and much more
* comprehensive error code returns solved this original problem.
*
* Most end-users will use buildkenel and the build tools from buildworld.
* The people that are inconvenienced by gratuitous bumps are developers
* who run config by hand.
Recognize a %VERSREQ=nnnnn string in the system Makefile. Both config(8) and the kernel will have a 'config interface version number'. If an incompatable change is made to the kernel that requires a rebuild of config(8) (such as the cam devtab stuff), then the version number would be bumped in both places. If a user neglects to rebuild config, then they will get a nagging (but non-fatal) warning that they need to rebuild config.
1997-10-22 00:38:48 +00:00
*
$Id$ -> $FreeBSD$
1999-08-28 01:35:59 +00:00
* $FreeBSD$
Recognize a %VERSREQ=nnnnn string in the system Makefile. Both config(8) and the kernel will have a 'config interface version number'. If an incompatable change is made to the kernel that requires a rebuild of config(8) (such as the cam devtab stuff), then the version number would be bumped in both places. If a user neglects to rebuild config, then they will get a nagging (but non-fatal) warning that they need to rebuild config.
1997-10-22 00:38:48 +00:00
*/
600004 is a better new version than 700000 based on some future commits to this file. With ru@'s approval, change it to this version. In this case we had to bump the version because the old parser would choke on | in the new 'or' syntax and consider that a device. Approved by: ru@
2005-11-28 17:47:54 +00:00
#define CONFIGVERS 600004
Add some rationale about when to bump and not bump the config version. Clarify that it is not like the shlib versions, and not like param.h's __FreeBSD_version/osreldate either. When config(8) was actively changing a while back, the interface between config and the build system (eg: /sys/conf/files.* and Makefile.*) was changing rapidly. configvers is a version number of that interface. User specified config files do not have a version number. The decision about whether a user supplied config file is syntactically valid or not belongs to the parser and sanity checks, not an arbitary number.
2005-11-07 17:37:27 +00:00
/*
* Examples of when there should NOT be a bump:
* - Adding a new keyword
* - Changing the syntax of a keyword such that old syntax will break config.
* - Changing the syntax of a keyword such that new syntax will break old
* config binaries.
*
* Examples of when there should be a bump:
* - When files generated in sys/$mach/compile/NAME are changed and the
* Makefile.$mach rules might not handle it correctly.
* - When there are incompatable changes to the way sys/conf/files.* or the
* other associated files are parsed such that they will be interpreted
* incorrectly rather than fail outright.
*/
Reference in New Issue Copy Permalink