From e0ae92a8485ecc027c84ecf5229f7fbb1d036a4e Mon Sep 17 00:00:00 2001 From: Tomasz Buchert Date: Sat, 29 Aug 2015 20:11:59 +0200 Subject: [PATCH] add a note about building official packages --- doc/debocker.8 | 11 +++++++---- doc/debocker.8.html | 22 +++++++++++++--------- doc/debocker.8.ronn | 12 ++++++++---- 3 files changed, 28 insertions(+), 17 deletions(-) diff --git a/doc/debocker.8 b/doc/debocker.8 index 707219d..072d5c2 100644 --- a/doc/debocker.8 +++ b/doc/debocker.8 @@ -1,7 +1,7 @@ .\" generated with Ronn/v0.7.3 .\" http://github.com/rtomayko/ronn/tree/0.7.3 . -.TH "DEBOCKER" "8" "July 2015" "Debian" "debocker" +.TH "DEBOCKER" "8" "August 2015" "Debian" "debocker" . .SH "NAME" \fBdebocker\fR \- build Debian packages with docker @@ -13,6 +13,9 @@ \fBDebocker\fR builds Debian packages inside docker\. The build process is contained in docker images and (almost) no other tools are needed to develop Debian packages on the main system\. Moreover, docker\'s image cache reuses the same system state whenever possible\. In particular, when a package is built for the second time, its dependecies and buildchain are not downloaded nor installed again\. . .P +\fBDo not use debocker to build packages that will will be uploaded to the Debian archive\fR, unless you use a trusted Debian base image (I mean it)\. Currently, \fBdebocker\fR uses Debian images from Docker registry which cannot be trusted for such use\. +. +.P \fBDebocker\fR is also able to create a self\-contained \fIbundle\fR with everything necessary to build a package with docker only\. . .P @@ -22,7 +25,7 @@ You do not have to be root to run \fBdebocker\fR, but you have to be able to use The build process consists of 5 steps: . .IP "1." 4 -\fIuprade\fR \- the base image is updated to the most recent packages (with apt\-get) +\fIupgrade\fR \- the base image is updated to the most recent packages (with apt\-get) . .IP "2." 4 \fIinstall\-utils\fR \- the Debian toolchain is installed @@ -187,7 +190,7 @@ Debocker does not clean after itself\. If you are not careful, docker images may And probably many more\. . .SH "AUTHOR" -Initial idea and coding has been done by Tomasz Buchert \fItomasz@debian\.org\fR\. +Initial idea and coding has been done by Tomasz Buchert\. . .P Initial packaging, many ideas and a lot of support by Dariusz Dwornikowski\. @@ -196,4 +199,4 @@ Initial packaging, many ideas and a lot of support by Dariusz Dwornikowski\. The semi\-official homepage is \fIhttp://debocker\.debian\.net\fR\. . .SH "SEE ALSO" -pbuiler(8), docker(1), devscripts(1), pristine\-tar(1) +pbuilder(8), docker(1), devscripts(1), pristine\-tar(1) diff --git a/doc/debocker.8.html b/doc/debocker.8.html index 7c8bcc4..006e885 100644 --- a/doc/debocker.8.html +++ b/doc/debocker.8.html @@ -89,6 +89,11 @@ image cache reuses the same system state whenever possible. In particular, when a package is built for the second time, its dependecies and buildchain are not downloaded nor installed again.

+

Do not use debocker to build packages that will will be uploaded to +the Debian archive, unless you use a trusted Debian base image (I +mean it). Currently, debocker uses Debian images from Docker +registry which cannot be trusted for such use.

+

Debocker is also able to create a self-contained bundle with everything necessary to build a package with docker only.

@@ -99,13 +104,13 @@ member of the docker group.

The build process consists of 5 steps:

    -
  1. uprade - the base image is updated to the most recent +
  2. upgrade - the base image is updated to the most recent packages (with apt-get)
    3. -
  3. install-utils - the Debian toolchain is installed
    4. -
  4. install-deps - the build dependencies of the package are +
  5. install-utils - the Debian toolchain is installed
    6. +
  6. install-deps - the build dependencies of the package are installed
    7. -
  7. extract-source - the source package is extracted
    8. -
  8. build - the proper build is executed
    9. +
  9. extract-source - the source package is extracted
    10. +
  10. build - the proper build is executed
@@ -235,8 +240,7 @@ images may consume a lot of space.

AUTHOR

-

Initial idea and coding has been done by Tomasz Buchert -tomasz@debian.org.

+

Initial idea and coding has been done by Tomasz Buchert.

Initial packaging, many ideas and a lot of support by Dariusz Dwornikowski.

@@ -245,12 +249,12 @@ Dwornikowski.

SEE ALSO

-

pbuiler(8), docker(1), devscripts(1), pristine-tar(1)

+

pbuilder(8), docker(1), devscripts(1), pristine-tar(1)

  1. Debian
    2. -
  2. July 2015
    3. +
  3. August 2015
  4. debocker(8)
diff --git a/doc/debocker.8.ronn b/doc/debocker.8.ronn index 215bd05..8fdbae9 100644 --- a/doc/debocker.8.ronn +++ b/doc/debocker.8.ronn @@ -14,6 +14,11 @@ image cache reuses the same system state whenever possible. In particular, when a package is built for the second time, its dependecies and buildchain are not downloaded nor installed again. +**Do not use debocker to build packages that will will be uploaded to +the Debian archive**, unless you use a trusted Debian base image (I +mean it). Currently, **debocker** uses Debian images from Docker +registry which cannot be trusted for such use. + **Debocker** is also able to create a self-contained *bundle* with everything necessary to build a package with docker only. @@ -23,7 +28,7 @@ member of the *docker* group. The build process consists of 5 steps: - 1. *uprade* - the base image is updated to the most recent + 1. *upgrade* - the base image is updated to the most recent packages (with apt-get) 2. *install-utils* - the Debian toolchain is installed 3. *install-deps* - the build dependencies of the package are @@ -151,8 +156,7 @@ And probably many more. ## AUTHOR -Initial idea and coding has been done by Tomasz Buchert -. +Initial idea and coding has been done by Tomasz Buchert. Initial packaging, many ideas and a lot of support by Dariusz Dwornikowski. @@ -161,4 +165,4 @@ The semi-official homepage is . ## SEE ALSO -pbuiler(8), docker(1), devscripts(1), pristine-tar(1) +pbuilder(8), docker(1), devscripts(1), pristine-tar(1) -- 2.20.1