d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b91d620462
freebsd-dev/release/doc/en_US.ISO8859-1/hardware/Makefile.inc

16 lines
533 B
PHP
Raw Normal View History

Change the way the value of DESTDIR is determined for the release notes build. Instead of having doc.relnotes.mk make a guess, hardcode quite a bit (but as little as possible) in Makefile.inc's sprinkled strategicly throughout the tree. This has the advantage of actually working properly (which is a Good Thing(tm)), and the disadvantages of more files in the repository and more hardcoded paths (which are both Bad Things(tm)).
2001-06-21 20:43:43 +00:00
# $FreeBSD$
If NO_LANGCODE_IN_DESTDIR is defined, don't put the language code in DESTDIR. This avoids redundant information in the path when DOCDIR points to some directory that already implies (or specifies) a certain language. This is the case with the web site, where the release notes are already installed under a language-specific directory. This behavior is not being made mandatory because it might still be useful to install all the translations in one directory, such as during testing, or in a hypothetical release notes archive. Furthermore, it is not being made the default because that breaks consistency with stuff under doc/. Reviewed by: bmah
2001-09-03 14:39:32 +00:00
.ifdef NO_LANGCODE_IN_DESTDIR
DESTDIR?= ${DOCDIR}/hardware/${.CURDIR:T}
.else
Change the way the value of DESTDIR is determined for the release notes build. Instead of having doc.relnotes.mk make a guess, hardcode quite a bit (but as little as possible) in Makefile.inc's sprinkled strategicly throughout the tree. This has the advantage of actually working properly (which is a Good Thing(tm)), and the disadvantages of more files in the repository and more hardcoded paths (which are both Bad Things(tm)).
2001-06-21 20:43:43 +00:00
DESTDIR?= ${DOCDIR}/en_US.ISO8859-1/hardware/${.CURDIR:T}
If NO_LANGCODE_IN_DESTDIR is defined, don't put the language code in DESTDIR. This avoids redundant information in the path when DOCDIR points to some directory that already implies (or specifies) a certain language. This is the case with the web site, where the release notes are already installed under a language-specific directory. This behavior is not being made mandatory because it might still be useful to install all the translations in one directory, such as during testing, or in a hypothetical release notes archive. Furthermore, it is not being made the default because that breaks consistency with stuff under doc/. Reviewed by: bmah
2001-09-03 14:39:32 +00:00
.endif
Auto generate the device listings in the Hardware Notes based on manual pages, to avoid duplicating work between the Hardware Notes and manual pages. Each text line in the output from the manual page parser is generated as a SGML entity, making it possible for translators to only translate lines which actually contains English text (this neat idea came from hrs). To determine which drivers are usable on which architectures the dev.archlist.txt file is used to explicitly list this. It it an imperfect solution, but the best I have been able to come up with for now. This commit converts most of the devices which has a section 4 manual page with a HARDWARE section to be the new auto generated format. Reviewed in principle by: ru, hrs, trhodes Good ideas for improvements: hrs No objections: -doc, re
2004-08-03 22:12:45 +00:00
# Force include of the autogenerated catalog. It has to be set
# directly in the CATALOG variable since doc.docbook.mk check if each
# catalog file exist for the other *CATALOG variables, and
# catalog-auto does not exist yet when that check is performed,
# causing catalog-auto not to be added to CATALOGS which breaks the
# build.
CATALOGS+= -c ${DEV-AUTODIR}/catalog-auto
Reference in New Issue Copy Permalink