DAPS(1)

πŸ’– DAPS πŸ’–

okay bestie, welcome to the daps manual page β€” this is DAPS(1), the one all about daps-autobuild, and we're gonna get you fully caught up. no skimming, no gatekeeping, we're doing this properly 🫢


✨ NAME ✨

daps-autobuild β€” automatically build books from several DAPS projects hosted on subversion or git. like, it just does that for you. iconic behavior honestly 🌸


✨ SYNOPSIS ✨

daps-autobuild {--config PATH_TO_CONFIG-FILE} [OPTIONS]

that's the vibe. one required thing in curly braces, everything else optional in square brackets. slay ✨


✨ DESCRIPTION ✨

so daps-autobuild is literally designed to automatically build/rebuild documents from several DAPS projects hosted on subversion or git. the build results (HTML, single HTML, and/or PDF β€” yes, all three, she contains multitudes πŸ’…) can be copied to a remote server using rsync. and if you run it regularly (like, e.g. via cron), rebuilds will only be triggered if changes in the project repository have actually occurred. no wasted work, no drama, we respect that πŸ”₯

daps-autobuild needs an XML configuration file providing all the data needed to build the books (see FIXME for details πŸ‘€). specifying this file with --config is mandatory β€” like, you cannot skip it, bestie. the script automatically validates the configuration file with each run, which is very main character of it. and if you wanna manually validate the configuration file? use --validate. easy πŸ’–


✨ OPTIONS ✨

  • --config PATH_TO_CONFIG-FILE β€” path to config file. can be specified relative or absolute, whichever floats your boat. Default: unset 🌸
  • --debug β€” if a build failure happens, show a verbose DAPS log so you can actually see what went wrong. Default: disabled πŸ›
  • --force β€” normally, documents will only be rebuilt if the Git/SVN repository has changed since the last build. use this option to force a rebuild even when the repository has not changed. Default: disabled (rebuilds on changes only) πŸ’ͺ
  • --help β€” display the script's help message. the classic ✨
  • --helpconfig β€” show help on the config file. yes queen, documentation for your documentation πŸŽ€
  • --nosync β€” do not rsync the manuals. Default: disabled (rsync will be done) πŸ¦‹
  • --notify β€” in case of build failures, send a notification to the e-mail address specified with <maintainer/> in the config file. ⚠️ it will be ignored if maintainer is not set. Default: disabled (no notification e-mails) πŸ“§
  • --schemaPATH_TO_SCHEMA-FILE β€” path to the schema used to validate the config file. Default: /usr/share/xml/daps/schema/daps-autobuild.rnc πŸ—‚οΈ
  • --sections SECT1 SECT2 ... β€” space-separated list of sets that should be build. the sets need to be configured in the config file. Default: not set (all sets from the config file will be build) πŸ“š
  • --validate β€” validate the config file specified with --config. other options except --schema will be ignored. periodt πŸ’…

✨ SEE ALSO ✨


✨ AUTHOR ✨

  • Frank Sundermeyer <fsundermeyer@opensuse.org> β€” Developer πŸ‘‘

ok so real talk, quick vibe check recap: --config is mandatory fr fr, and if you want your config validated manually it's --validate but it ignores everything except --schema. don't forget πŸ’–

this whole thing is DAPS @DAPS_VERSION@, dated 11/06/2025, and it lives in section DAPS(1) of your manual. that's a wrap bestie, go build some books, you've got this πŸ‘‘πŸŒˆπŸ’œ

πŸ“¦ where this page comes from