man: Rebuild documentation

Signed-off-by: Ikey Doherty <ikey@solus-project.com>

Author: ikeydoherty

man/package.yml.5

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "PACKAGE\.YML" "5" "December 2016" "" ""
+.TH "PACKAGE\.YML" "5" "May 2017" "" ""
 .
 .SH "NAME"
 \fBpackage\.yml\fR \- Solus package build format
@@ -246,6 +246,18 @@ All files captured by this expression will then end up in that subpackage\. Each
 \fBypkg\-build(1)\fR ensures that a file cannot belong to multiple packages, and that the last specified pattern, if matching, ALWAYS wins\. It is even possible to supress generation of the main package, by pattern globbing \fB/*\fR to a subpackage\. This will not cause any breakage\.
 .
 .IP "\(bu" 4
+\fBpermanent\fR [list]
+.
+.IP
+A list of patterns used to mark files as permanent\. Any file within the resulting binary packages that matches the path pattern, is marked as a permanent file\.
+.
+.IP
+These files will not be removed from the filesystem when upgrading or reinstalling the package\. They will persist during standard upgrade operations\.
+.
+.IP
+This should only be used in critical chain packages such as the kernel or drivers, where the domain of control is outside of the package manager, and the package is simply used as an update delivery mechanism\.
+.
+.IP "\(bu" 4
 \fBstrip\fR [boolean]
 .
 .IP
@@ -258,6 +270,15 @@ In most cases, stripping should remain enabled\. However, there are known cases
 The Go programming language generates \fB*\.a\fR archive files that under no circumstance should be stripped, and there are likely other cases\. This key, when set to \fBno\fR, will disable any and all stripping\.
 .
 .IP "\(bu" 4
+\fBdebug\fR [boolean]
+.
+.IP
+By default, this key is enabled, and as a result \fBypkg\-build(1)\fR will automatically create resulting \fB\-dbginfo\fR packages where it can\.
+.
+.IP
+In the majority of cases, this is the desired behaviour in full build environments, such as a build server\. However in very rare cases, this may cause problems for the package, especially if it contains binaries that have not been bootstrapped with the native toolchain\.
+.
+.IP "\(bu" 4
 \fBavx2\fR [boolean]
 .
 .IP

man/package.yml.5.html

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "YPKG\-BUILD" "1" "December 2016" "" ""
+.TH "YPKG\-BUILD" "1" "May 2017" "" ""
 .
 .SH "NAME"
 \fBypkg\-build\fR \- Build Solus ypkg files

man/ypkg-build.1

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "YPKG\-INSTALL\-DEPS" "1" "December 2016" "" ""
+.TH "YPKG\-INSTALL\-DEPS" "1" "May 2017" "" ""
 .
 .SH "NAME"
 \fBypkg\-install\-deps\fR \- Install build dependencies

man/ypkg-build.1.html

@@ -1,7 +1,7 @@
 .\" generated with Ronn/v0.7.3
 .\" http://github.com/rtomayko/ronn/tree/0.7.3
 .
-.TH "YPKG" "1" "December 2016" "" ""
+.TH "YPKG" "1" "May 2017" "" ""
 .
 .SH "NAME"
 \fBypkg\fR \- Build Solus ypkg files