+++ /dev/null
-.\" Man page for e2-build
-.\"
-.\" (c)2007, 2008 emlix GmbH
-.\"
-.TH e2-build 1 "Dec 1, 2008" "2.2"
-
-.SH NAME
-e2-build \- build results from repository or local sources
-
-.SH SYNOPSIS
-e2-build [OPTION|RESULT ...]
-
-.SH DESCRIPTION
-\fBe2-build\fR builds one or more results,
-dependencies are taken into account.
-Depending on the intended outcome, different versions of the source
-files to use may be retrieved for the build process.
-See \fBe2config\fR for a description of the source config file format.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-build-mode=MODE
-results can be built according to different build modes, as defined by the
-(currently builtin) policy module.
-A build mode sets the class of sources to take, and influences the buildid,
-the dependencies used and the place to store results.
-.TP
-.BR \-\-branch-mode
-build selected results in 'branch' build-mode.
-.TP
-.BR \-\-wc-mode
-build selected results in 'working-copy' build-mode.
-.TP
-.BR \-\-all
-Possibly build all results listed in the dependencies.
-This is the default when building from repository sources.
-.TP
-.BR \-\-playground
-Prepare build environment but do not start the build script. The build
-environment can later be entered using the \fBe2-playground\fR tool.
-.TP
-.BR \-\-keep
-Do not remove the \fBchroot\fR(1) environment after a build (regardless
-of whether it is successful or not).
-.TP
-.BR \-\-help
-Show usage information.
-
-.P
-Valid build modes according to the builtin policy are
-\fBworking-copy\fR, \fBtag\fR, \fBrelease\fR and \fBbranch\fR.
-\fBtag\fR is the default build mode. \fBrelease\fR is exactly the same
-as \fBtag\fR but the results will be stored in a special location on the
-server side. (To be archived, separated from lots of results built
-for testing.)
-
-.P
-To use the branch from the scm source configuration for selected results
-build in 'tag' mode, and select the results to build in branch-mode.
-
-.SH Examples:
-build selected results from their source branches. Dependencies not selected
-on the command line are built in the default build-mode.
-.IP
-e2-build --branch-mode <result> ...
-.PP
-build a release
-.IP
-e2-build --build-mode=release
-.PP
-build
-.IP
-e2-build
-.PP
-
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-ls-project (1),
-.BR e2-playground (1),
-.BR e2config (5),
-.BR e2-runbuild (1).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007, 2008 emlix GmbH
--- /dev/null
+.\" Man page for e2-build
+.\"
+.\" (c)2007, 2008, 2012 emlix GmbH
+.\"
+.TH e2-build 1 "Oct 26, 2012" "@VERSION@"
+
+.SH NAME
+e2-build \- build results of an e2factory project
+
+.SH SYNOPSIS
+e2-build [<option>] [<result> ...]
+
+.SH DESCRIPTION
+\fBe2-build\fR is part of the e2factory commandline tools.
+.br
+\fBe2-build\fR builds one or more results as defined in the build-script in a chroot and stores the resulting files.
+If no result is given, all results listed in "default\_results" in proj/config are built, see
+\fBe2project\fR(5).
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero. Consult the log-files in the log/ directory of the
+e2factory project for further information.
+
+.SH OPTIONS
+.TP
+.BR \-\-all
+Build all results configured in the project.
+.TP
+.BR "\-\-build-mode=release", " \-\-release"
+ Build selected results in "release" build-mode.
+.TP
+.BR "\-\-build-mode=tag", " \-\-tag"
+ Build selected results in "tag" build-mode. Default.
+.TP
+.BR "\-\-build-mode=branch", " \-\-branch"
+ Build selected results in "branch" build-mode.
+.TP
+.BR "\-\-build-mode=working-copy", " \-\-working-copy"
+ Build selected results in "working-copy" build-mode.
+.TP
+.BR \-\-check
+Performs all checks that can be done without server access.
+This option works only with results which are built in "tag" build-mode.
+.TP
+.BR \-\-check-remote
+This will perform all check that can be done with server access.
+This option works only results which are build in tag mode.
+.TP
+.BR "\-\-branch-mode <result> ..."
+Build all selected results in "branch" build-mode.
+.TP
+.BR "\-\-wc-mode <result> ..."
+Build all selected results in "working-copy" build mode.
+.TP
+.BR \-\-playground
+Prepare build environment but do not start the build script. The build
+environment can later be entered using the \fBe2-playground\fR tool.
+.TP
+.BR \-\-keep
+Do not remove the \fBchroot\fR(1) environment after a build (regardless of whether it is successful or not).
+.TP
+.BR \-\-force-rebuild
+Forces e2factory to rebuild a result even if a result with the same buildID already exists.
+It is recommend to not use it.
+.TP
+.BR \-\-buildid
+Display all buildIDs without actually building any results.
+.TP
+.BR \-\-enable-writeback
+This option overrides the writeback option from server configuration and set it to enable.
+.TP
+.BR \-\-disable-writeback
+This option overrides the writeback option from server configuration and set it to disable.
+.TP
+For further global options and environment variables, see \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Just build all default results and all results they depend on, in case not already built:
+.IP
+.nf
+e2-build
+.fi
+.PP
+Display buildID of result "foo" and all results it depends on:
+.IP
+.nf
+e2-build --buildid foo
+.nf
+
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for <tool>
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH <tool> 1 "Dec 12, 2007" "2.1"
-
-.SH NAME
-e2-cf \- modify and create configuration files
-
-.SH SYNOPSIS
-usage: e2 cf <command> ...
-
-.SH DESCRIPTION
-commands are:
- newresult <name>
- newsource <name> <scm>
- editresult <name>
- editbuildscript <name>
- editsource <name>
-
-Commands starting with 'edit' can be abbreviated by using e...
-Commands starting with 'new' can be abbreviated by using n...
-Commands can be shortened as long as they remain unambiguous
-
-e.g.: eb <name> is equivalent to editbuildscript <name>
-
-Templates are used as initial config files. An editor is started
-for each file that must be configured by the user.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH EXAMPLES
-The following three commands do exactly the same: Create a new result
-configuration for a result named 'foo':
-.IP
-.nf
-e2-cf newresult foo
-e2-cf newr foo
-e2-cf nr foo
-.PP
-
-.SH ENVIRONMENT
-e2-cf uses the EDITOR environment variable to determine which editor to
-start. The default editor is 'vi'.
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-cf
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-cf 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-cf \- modify and create configuration files of an e2factory project
+
+.SH SYNOPSIS
+e2-cf <command> <arguments> ...
+
+.SH DESCRIPTION
+\fBe2-cf\fR is part of the e2factory commandline tools.
+.br
+\fBe2-cf\fR starts an editor and opens appropriate configuration files for
+further modification. Templates are used as initial config files.
+.br
+Commands are:
+ newresult <name>
+ newsource <name> <scm>
+ editresult <name>
+ editbuildscript <name>
+ editsource <name>
+
+Commands can be shortened as long as they remain unambiguous.
+.br
+e.g.: "eb <name>" is equivalent to "editbuildscript <name>".
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+For options, see global options in \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Create a new source configuration, named "bar", see also \fBe2-new-source\fR(1):
+.IP
+.nf
+e2-cf ns bar
+.fi
+.PP
+Create a new result configuration for a result named "foo":
+.IP
+.nf
+e2-cf nr foo
+.fi
+.PP
+Adopt the configuration:
+.IP
+.nf
+e2-cf er foo
+.fi
+.PP
+Adopt the build-script:
+.IP
+.nf
+e2-cf eb foo
+.fi
+
+.SH ENVIRONMENT
+Following environment variables are evaluated:
+.TP
+.BR EDITOR
+Defines the editor to be started. The default editor is "vi".
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-create-project
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-create-project 1 "Aug 6, 2007" "0.1"
-
-.SH NAME
-e2-create-project \- create a new project
-
-.SH SYNOPSIS
-e2-create-project [<option> ...] [<server>:]<location>
-
-.SH DESCRIPTION
-Create a new project and store it on <server> in <location>.
-<server> defaults to 'projects'.
-The project name will be the basename of <location>.
-The usual project location convention is
-\fBprojects:<customer>/<projectname>\fR.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.TP
-.BR \-\-version
-Show version number of e2.
-
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro(7)
-.BR e2global(7)
-.BR e2-fetch-project(1)
-.BR e2-fetch-sources(1)
-.BR e2-ls-project(1)
-.BR e2config(5)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-create-project
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-create-project 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-create-project \- create a new e2factory project
+
+.SH SYNOPSIS
+e2-create-project [<option> ...] [<server>:]<location>
+
+.SH DESCRIPTION
+\fBe2-create-project\fR is part of the e2factory commandline tools.
+.br
+It creates a new project and stores it on <server> in <location>.
+<server> defaults to server "projects" as configured in e2.conf(5).
+The project name will be the basename of <location>.
+The usual project location convention is
+\fBprojects:<customer>/<projectname>\fR.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+\fBe2-create-project\fR does only receive global options, see \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Create a new project:
+.IP
+.nf
+e2-create-project foo/bar
+.fi
+
+.SH ENVIRONMENT
+Following environment variables are evaluated:
+.TP
+.BR E2_LOCAL_BRANCH
+Branch of version of e2factory to be used.
+.TP
+.BR E2_LOCAL_TAG
+Tag of version of e2factory to be used.
+
+
+.SH SEE ALSO
+.BR e2factory(1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-dlist
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-dlist 1 "Aug 3, 2007" "0.1"
-
-.SH NAME
-e2-dlist \- list dependencies of a particular result
-
-.SH SYNOPSIS
-e2-dlist [OPTION|RESULT ...]
-
-.SH DESCRIPTION
-\fBe2-dlist\fR shows the direct dependencies of a result, i.e. the
-results that are required to be built before the argument result can
-be created. In other words, the listed results are
-\fBbuild-time dependencies\fR of the argument result.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-recursive
-Show indirect dependencies as well. Normally only direct dependencies
-are shown.
-.TP
-.BR \-\-help
-Show usage information.
-
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-dsort (1),
-.BR e2-ls-project (1),
-.BR e2config (5).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-dlist
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-dlist 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-dlist \- list dependencies of a particular result of an e2factory project
+
+.SH SYNOPSIS
+e2-dlist [option] <result>...
+
+.SH DESCRIPTION
+\fBe2-dlist\fR is part of the e2factory commandline tools.
+.br
+\fBe2-dlist\fR shows the direct dependencies of a result, i.e. the
+results that are required to be built before the <result> can
+be build.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+.BR \-\-recursive
+Show indirect dependencies as well.
+.TP
+For further global options, see \fBe2factory\fR(1).
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-dsort
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-dsort 1 "Aug 3, 2007" "0.1"
-
-.SH NAME
-e2-dsort \- sort result dependencies
-
-.SH SYNOPSIS
-e2-dsort [OPTION ...]
-
-.SH DESCRIPTION
-\fBe2-dsort\fR lists the results of the current project, sorted in the
-order in which they must be built.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-dlist (1),
-.BR e2-ls-project (1),
-.BR e2config (5).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-dsort
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-dsort 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-dsort \- sort result dependencies of an e2factory project
+
+.SH SYNOPSIS
+e2-dsort [<option>]
+
+.SH DESCRIPTION
+\fBe2-dsort\fR is part of the e2factory commandline tools.
+.br
+\fBe2-dsort\fR lists the results of the current project, sorted in the
+order in which they must be built.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+\fBe2-dsort\fR does only receive global options, see \fBe2factory\fR(1).
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-fetch-project
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-fetch-project 1 "Aug 6, 2007" "0.1"
-
-.SH NAME
-e2-fetch-project \- retrieve project file structure
-
-.SH SYNOPSIS
-e2-fetch-project [OPTION]... PATH [DESTINATION]
-
-.SH DESCRIPTION
-\fBe2-fetch-project\fR clones a project repository designated by "PATH",
-which should be the absolute path to a \fBe2(7)\fR project. The usual
-project path convention is \fB/<server-project-dir>/<customer>/<projectname>\fR.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.TP
-.BR \-\-version
-Show version number of e2.
-.TP
-.BR \-\-branch=BRANCHNAME
-Checks out a specfic project branch.
-
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro(7)
-.BR e2global(7)
-.BR e2-create-project(1)
-.BR e2-install-e2(1)
-.BR e2-fetch-sources(1)
-.BR e2-ls-project(1)
-.BR e2config(5)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-fetch-project
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-fetch-project 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-fetch-project \- retrieve an e2factory project
+
+.SH SYNOPSIS
+e2-fetch-project [<option> ...] [<server>:]<location> [destination]
+
+.SH DESCRIPTION
+\fBe2-build\fR is part of the e2factory commandline tools.
+.br
+\fBe2-fetch-project\fR fetches the e2factory project located in
+[<server>]:<location> to a directory given in <destination>.
+.br
+<server> defaults to "projects". As configured in e2.conf(5).
+.br
+<destination> defaults to ".".
+.br
+The projects main git repository is cloned and the configured version of e2factory is locally
+installed.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+.BR \-\-branch=<branch>
+Checks out a specific project branch.
+.TP
+.BR \-\-tag=<tag>
+Checks out a specific project tag.
+.TP
+For further global options, see \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Retrieve a project.
+.IP
+.nf
+e2-fetch-project foo/bar
+.fi
+
+
+.SH SEE ALSO
+.BR e2factory(1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-fetch-sources
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-fetch-sources 1 "Aug 3, 2007" "0.1"
-
-.SH NAME
-e2-fetch-sources \- retrieve sources for the current project
-
-.SH SYNOPSIS
-e2-fetch-sources [OPTION|SOURCE|RESULT ...]
-
-.SH DESCRIPTION
-\fBe2-fetch-sources\fR retrieves sources for project results. Sources can be
-either specified through the source- or result names. For sources stored
-in version-controlled repositories, the associated repositories will be
-cloned and a project-local working copy created.
-
-Note, that sources of type \fIfiles\fR are not fetched.
-
-Note, that sources are not fetched again, where fetched yet.
-Moreover, the local working copy at \fIin/SOURCE\fR is not checked for
-up-to-dateness.
-Thus, to refetch sources, remove the outdated working copy,
-then fetch again.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-all
-Fetch all sources refered to in the whole project.
-.TP
-.BR \-\-source
-Fetch sources by source name.
-.TP
-.BR \-\-result
-Fetch sources by result name.
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-ls-project (1),
-.BR e2config (5),
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-fetch-sources
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-fetch-sources 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-fetch-sources \- retrieve sources of an e2factory project
+
+.SH SYNOPSIS
+e2-fetch-sources [<option> ... | <source> ... | <result> ...]
+
+.SH DESCRIPTION
+\fBe2-fetch-sources\fR is part of the e2factory commandline tools.
+\fBe2-fetch-sources\fR can operate in two modes, fetch and update.
+
+The \fBfetch\fR mode retrieves sources. Sources can be
+either specified through the source- or result names. Sources stored
+in SCM repositories will be cloned and a project-local working copy
+will be created. Already fetched source are not updated in the
+\fBfetch\fR mode. See below.
+
+The \fBupdate\fR mode is currently limited to the git SCM and updates
+remote branches without touching the working-copy. That way additional
+tags from the server side repository become available while users work is preserved.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+.BR \-\-fetch
+\fBe2-fetch-sources\fR works in fetch mode. This is default.
+.TP
+.BR \-\-update
+\fBe2-fetch-sources\fR works in update mode.
+.TP
+.BR \-\-all
+Fetch all sources referred to in the whole project.
+.TP
+.BR \-\-scm
+Fetch all sources referred by a SCM. This excludes file sources.
+.TP
+.BR \-\-files
+Select files sources. Not selected by default.
+.TP
+.BR \-\-git
+Fetch sources from a git repository.
+.TP
+.BR \-\-svn
+Fetch sources from a svn repository.
+.TP
+.BR \-\-cvs
+Fetch sources from a cvs repository.
+.TP
+.BR \-\-source
+Fetch sources by source name.
+.TP
+.BR \-\-result
+Fetch sources by result name.
+.TP
+.BR \-\-chroot
+Select chroot files.
+.TP
+For further global options, see \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Download all sources and other needed files of an e2factory project.
+.IP
+.nf
+e2-fetch-sources --all
+.fi
+.PP
+Update all sources.
+.IP
+.nf
+e2-fetch-sources --update
+.fi
+
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-install-e2
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-install-e2 1 "Sep 11, 2007" "0.2"
-
-.SH NAME
-e2-install-e2 \- install the e2 local tools into a project environment
-
-.SH SYNOPSIS
-e2-install-e2
-
-.SH DESCRIPTION
-\fBe2-install-e2\fR reads the required e2 version from the
-\fB.e2/e2version\fR file and installs that version of e2 into the local
-project environment.
-
-The \fB.e2/e2version\fR file has a single line with this format:
-
- <branch> <tag>
-
-By default the tagged version of e2 is installed.
-
-To enable the project developers to follow a stable branch of the
-e2 local tools, the tag may be ^ unless a release shall be built.
-In this case the HEAD of the branch is installed. In this case
-the e2 local tools change if commits are done to that branch.
-
-That is analog to source configurations in the project repository.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.TP
-.BR \-\-version
-Show version number of e2.
-
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro(7)
-.BR e2global(7)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-install-e2
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-install-e2 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-install-e2 \- install the e2factory local tools into a project environment
+
+.SH SYNOPSIS
+e2-install-e2 [<option>
+
+.SH DESCRIPTION
+\fBe2-install-e2\fR is part of the e2factory commandline tools.
+.br
+\fBe2-install-e2\fR reads the \fB.e2/e2version\fR and \fB.e2/extensions\fR files and
+installs the configured versions of e2factory and its extensions into the local project environment.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+\fBe2-install-e2\fR does only receive global options, see \fBe2factory\fR(1).
+
+.SH SEE ALSO
+.BR e2factory(7)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
--- /dev/null
+.\" Man page for e2-locate-project-root
+.\"
+.\" (c)2007, 2008, 2012 emlix GmbH
+.\"
+.TH e2-locate-project-root 1 "Oct 26, 2012" "@VERSION@"
+
+.SH NAME
+e2-locate-project-root \- print out the project root of an e2factory project
+
+.SH SYNOPSIS
+e2-locate-project-root
+
+.SH DESCRIPTION
+\fBe2-locate-project-root\fR is part of the e2factory commandline tools.
+.br
+\fBe2-locate-project-root\fR displays the root directory of the current project.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+\fBe2-locate-project-root\fR does not receive any options.
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-ls-project
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-ls-project 1 "Aug 6, 2007" "0.1"
-
-.SH NAME
-e2-ls-project \- show project information
-
-.SH SYNOPSIS
-e2-ls-project [OPTION]...
-
-.SH DESCRIPTION
-\fBe2-ls-project\fR displays the configuration and components of the
-current project and can report the current build status of results.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-status
-Show build status of all results.
-.TP
-.BR \-\-all
-Show all sources and results, even if not currently used by the project.
-.TP
-.BR \-\-offline
-Do not check or print data that reside on a server.
-.TP
-.BR \-\-dot
-Generate \fBdot\fR(1) graph from source and result dependencies.
-.TP
-.BR \-\-licences
-Lists licences used in this project and their paths.
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2config (5).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-ls-project
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-ls-project 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-ls-project \- show project information of an e2factory project
+
+.SH SYNOPSIS
+e2-ls-project [<option>]... [<result> ]
+
+.SH DESCRIPTION
+\fBe2-ls-project\fR is part of the e2factory commandline tools.
+.br
+\fBe2-ls-project\fR displays the configuration and components of the
+current e2factory project.
+
+If <result> is given, reduce output to that result and all results it depends on.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+.BR \-\-all
+Show all sources and results, even if not currently used by the project.
+.TP
+.BR \-\-dot
+Generate graph for processing with graphviz, see dot(1).
+.TP
+.BR \-\-dot-sources
+As "\-\-dot", but also show sources.
+.TP
+.BR \-\-swap
+Swaps the direction of the graphs.
+.TP
+For further global options, see \fBe2factory\fR(1).
+
+.SH EXAMPLES
+Generate a graph and convert it to pdf.
+.IP
+.nf
+e2-ls-project --dot | dot -Tpdf > project.pdf
+.fi
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
.\" Man page for e2-new-source
.\"
-.\" (c)2007 emlix GmbH
+.\" (c)2007, 2012 emlix GmbH
.\"
-.TH e2-new-source 1 "Oct 23, 2007" "0.2"
+.TH e2-new-source 1 "Oct 16, 2012" "@VERSION@"
.SH NAME
-e2-new-source \- create a new source at a shared server location
+e2-new-source \- create a new source at a shared server location to be used in an e2factory project
.SH SYNOPSIS
e2-new-source --git [--server <server>] <name>
-e2-new-source --files [--no-checksum] [<server>:]<location> <source_file> [<checksum_file>]
+e2-new-source --files [--no-checksum] [<server>:]<location> <source_file_url> [<checksum_file_url>]
.SH DESCRIPTION
+\fBe2-new-source\fR is part of the e2factory commandline tools.
+.br
\fBe2-new-source\fR creates a new source repository or stores a file plus
checksum file in a location on a server.
-The type of the new source must be given, either --files or --git
-cvs and subversion do not support auto-creation of repositories for now.
+The type of the new source must be given, either --files or --git.
+cvs and subversion are not supported.
When creating a git repository a server side repository is created and
a local repository is created and set up to be related to the server side
-repository via the remote named origin.
+repository.
+
No commits are initially created. The user must create the initial commit
-and push it to the server. See Examples below.
+and push it to the server. See examples below.
-e2-new-source(1) does not create any configuration files. Use e2-cf(1) to
+\fBe2-new-source\fR does not create any configuration files. Use \fBe2-cf\fR(1) to
create a source configuration.
+Note that URLs must be passed as the <source_file_url> and
+ <checksum_file_url> arguments, not file system paths. See examples below.
+
.SH RETURN VALUE
Normally, exit status is 0. On error, it is non-zero.
.SH OPTIONS
.TP
.BR \-\-git
-Create a \fBgit\fR(7) repository at SERVERPATH.
+Put a repository named <name> into the project's "git/" directory on
+the server, i.e. <server>/<project>/git/<name>.git
+The server defaults to "projects" as configured e2.conf(5).
+.TP
+.BR \-\-server=<server>
+Specify server for git repository defaults to "projects" as configured e2.conf(5).
.TP
.BR \-\-files
-Create a \fBtar\fR(1) archive file source at SERVERPATH.
+ Put a new file onto the server.
+ Server defaults to "upstream" as configured e2.conf(5).
.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
+.BR \-\-no-checksum
+Do not verify checksum, <checksum_file_url> could be omitted.
+.TP
+For further global options and environment variables, see \fBe2factory\fR(1).
.SH EXAMPLES
To place an external source file on the default server:
.IP
-e2-new-source --files a/anything/0.1 file:///tmp/download/anything-0.1.tar.bz2
-file:///tmp/download/anything-0.1.tar.bz2.sha1
+.nf
+e2-new-source --files a/anything/0.1 file:///tmp/download/anything-0.1.tar.bz2 file:///tmp/download/anything-0.1.tar.bz2.sha1
+.fi
.PP
To create a new, empty git repository on server and client side:
.IP
-e2-new-source --git test2
+.nf
+e2-new-source --git test
+.fi
.PP
To populate the empty repository from an existing repository:
.IP
.nf
-cd in/<source>
+cd in/test
git fetch /path/to/original/repo <branch>:refs/heads/master
git push origin master
.fi
To populate the empty repositories with new sources:
.IP
.nf
-cd in/<source>
+cd in/test
# create source files, e.g. main.c
git add .
git commit -m 'initial commit'
git push origin master
.fi
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-ls-project (1),
-.BR e2config (5).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
+.SH SEE ALSO
+.BR e2factory (1)
.SH COPYRIGHT
-(c)2007 emlix GmbH
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2-playground
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-playground 1 "Aug 9, 2007" "0.1"
-
-.SH NAME
-e2-playground \- enter chroot(1) environment for specified result
-
-
-.SH SYNOPSIS
-e2-playground OPTION|RESULT ...
-
-.SH DESCRIPTION
-\fBe2-playground\fR enters a \fBchroot\fR(1) environment previously
-created by running \fBe2-build\fR with the "--playground" option, or
-one that is left over from a previous (possibly failed) build.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-command\=CMD
-Execute \fBCMD\fR in the chroot(1) environment, instead of running
-an interactive shell.
-.TP
-.BR \-\-showpath
-Print path to chroot(1) environment.
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7),
-.BR e2-ls-project (1),
-.BR e2-build (1),
-.BR e2config (5),
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
--- /dev/null
+.\" Man page for e2-playground
+.\"
+.\" (c)2007, 2012 emlix GmbH
+.\"
+.TH e2-playground 1 "Oct 16, 2012" "@VERSION@"
+
+.SH NAME
+e2-playground \- enter chroot(1) environment for specified result of an e2factory project
+
+
+.SH SYNOPSIS
+e2-playground [<option> ...] <result>
+
+.SH DESCRIPTION
+\fBe2-playground\fR is part of the e2factory commandline tools.
+.br
+\fBe2-playground\fR enters a chroot(1) environment previously
+created by running \fBe2-build\fR with the "--playground" option, or
+one that is left over from a previous failed build process or a build process with "--keep".
+It starts a chrooted interactive shell, that is expected to be part of the chroot.
+
+.SH RETURN VALUE
+Normally, exit status is 0. On error, it is non-zero.
+
+.SH OPTIONS
+.TP
+.BR "\-\-command \fRcmd"
+Execute \fBcmd\fR in the chroot(1) environment, instead of running
+an interactive shell.
+.TP
+.BR \-\-showpath
+Print path to chroot(1) environment.
+.TP
+.BR \-\-runinit
+Run init files automatically.
+.TP
+For further global options, see \fBe2factory\fR(1).
+
+.SH SEE ALSO
+.BR e2factory (1)
+
+.SH COPYRIGHT
+(c)2013 emlix GmbH
+++ /dev/null
-.\" Man page for e2
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2 1 "Aug 2, 2007" "0.1"
-
-.SH NAME
-e2 \- wrapper script for e2 build tools
-
-.SH SYNOPSIS
-e2 OPTION ...
-.br
-e2 COMMAND ARGUMENT ...
-
-.SH DESCRIPTION
-\fBe2\fR is a wrapper script for invoking \fBe2\fR commands. Any
-\fBe2\fR commands called will be redirected either to the
-project-local or the global installation, depending on whether the
-invocation took place inside or outside a project tree.
-
-.SH RETURN VALUE
-Depends on invoked subtool or 0 if an unknown command was given.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.TP
-.BR \-\-version
-Show version number of e2.
-.TP
-.BR \-\-prefix
-Print installation prefix and exit.
-
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro(7)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
+++ /dev/null
-.\" Man page e2-global
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2-global 7 "Sep 11, 2007" "0.2"
-
-.SH NAME
-e2global \- e2 global tools
-
-.SH DESCRIPTION
-There is a set of global tools with a well-defined interface to
-projects stored on a server and projects checked out as a working
-copy.
-This interface is versioned using files named \fBversion\fR in the
-project directory on the server, and \fB.e2/version\fR in the project
-repository.
-These files store integer version ids. They state which version of
-global code may be used to perform certain tasks on a project.
-
-.nf
-The interfaces cover:
- * how to create a project
- * how to checkout a project from the server
- * how to install the local e2 tools into a project
- * how to call local tools
-.fi
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2-fetch-sources(1)
-.BR e2-create-project(1)
-.BR e2(1)
-.BR e2intro(7)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
+++ /dev/null
-.\" General man page for e2
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2intro 7 "Aug 3, 2007" "0.1"
-
-.SH NAME
-e2 \- a system for automated and reproducible builds
-
-.SH DESCRIPTION
-\fBe2\fR is a system for building software from sources in a chroot(1)
-environment. The results of a build are fully reproducible and care is
-taken to avoid re-builds unless they would influence the outcome.
-Dependencies among build components are tracked and automatically
-handled by e2.
-
-.SH TERMINOLOGY
-
-.TP
-.BR result
-Designates something that is the product of executing a "build-script"
-with a given set of input "sources". Usually a set of binaries or a
-root file system.
-
-.TP
-.BR source
-Something that is the input to a build process. Usually this means a set
-of source files.
-.TP
-.BR project
-A "project" is a collection of sources, results and a description of their
-interdependencies. When the documentation refers to a \fBcurrent\fR
-project, then the project tree in which a particular e2 command is
-executed is meant.
-.TP
-.BR mode
-A mode in which a result is built, either "tag", "head" or "working-copy".
-.TP
-.BR backing store
-One or more locations that are used to store sources and build results,
-usually shared by several developers.
-
-.SH TOOLS
-e2 is used from the command line and provides the following tools to
-configure a project and run the build process:
-
-.SH GLOBAL TOOLS
-.TP
-.BR e2
-Call local tools.
-.TP
-.BR e2-create-project
-Create a new project in the backing store.
-.TP
-.BR e2-fetch-project
-Retrieves a project from the backing store.
-.TP
-.BR e2-install-e2
-Install the local e2 tools into a project environment.
-.TP
-.BR e2-su-*
-Provide root privileges for some actions.
-
-.SH LOCAL TOOLS
-.TP
-.BR e2-build
-Depending on options, builds a particular result or all,
-either using the state of the sources as stored in the
-current working copy, or the appropriate revision from the
-corresponding repository, when the source is located in a version controlled
-repository.
-.TP
-.BR e2-dlist
-Shows a sorted list of the dependencies for a given result.
-.TP
-.BR e2-dsort
-Shows the sorted list of results in the order in which they must be built
-to satisfy interdependencies among each result.
-.TP
-.BR e2-fetch-sources
-Retrieves the sources for the current project from the backing store.
-.TP
-.BR e2-ls-project
-Displays a schematic view of the current project and shows the project build status.
-.TP
-.BR e2-new-source
-Create a new source in the backing store.
-.TP
-.BR e2-playground
-Enter chroot environment previously created via
-\fBe2-build\ \-\-playground\fR.
-
-.TP
-All tools support the following common set of options:
-
-.TP
-.BR \-\-help
-Show usage information.
-.TP
-.BR \-\-version
-Show e2 version number and exit.
-.TP
-.BR \-\-quiet
-Disable all output to console.
-.TP
-.BR \-\-verbose
-Show information about what the tool is currently doing.
-.TP
-.BR \-\-debug
-Show complete debug information giving as much output as possible,
-as long as it concerns the current project.
-.TP
-.BR \-\-tooldebug
-Show complete debug information, including tool internal information.
-.TP
-.BR \-\-e2\-config
-Specify a e2 config file
-
-.SH ENVIRONMENT
-.TP
-.BR E2_CONFIG
-use a custom e2 config file
-.TP
-.BR E2_SSH
-specify a tool to use instead of \fBssh\fR(1).
-
-.SH "SEE ALSO"
-.BR e2workflow(7)
-.BR e2-build(1)
-.BR e2-cf(1)
-.BR e2-dlist(1)
-.BR e2-dsort(1)
-.BR e2-fetch-sources(1)
-.BR e2-ls-project(1)
-.BR e2-fetch-project(1)
-.BR e2-new-source(1)
-.BR e2-create-project(1)
-.BR e2config(5)
-.BR e2global(1)
-.BR e2-install-e2(1)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
+++ /dev/null
-.\" Man page for e2workflow
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH e2workflow 7 "Aug 2, 2007" "0.1"
-
-.SH NAME
-e2workflow \- common use cases and workflows for the e2 build system
-
-.SH "CREATING A NEW PROJECT"
-e2-create-project
-
-.SH "RETRIEVING A PROJECT THAT ALREADY EXISTS"
-e2-fetch-project
-.br
-e2-fetch-sources
-
-.SH "TAKING A LOOK"
-e2-ls-project
-.br
-e2-dlist
-.br
-e2-dsort
-
-.SH "ADDING NEW PACKAGES TO A PROJECT"
-e2-new-source
-
-.SH "BUILDING RESULTS"
-e2-build
-
-.SH "THE PLAYGROUND"
-e2-playground
-
-.SH "SOURCE REPOSITORY MAINTENANCE"
-git/svn
-
-.SH "REMOVING RESULTS OR SOURCES"
-nn
-
-.SH "WRITING HOOKS"
-nn
-
-.SH "USING EXTERNAL REPOSITORIES"
-All data used by the e2 tool is accessed via file system,
-as it is supposed to reside local.
-Where non local data is accessible via \fBnfs\fR(5), it
-can be used, though.
-
-However, an external source repository which is not accessible
-via nfs, is not available to e2 directly.
-It is up to the project coordination to set up a configuration
-where data from an external sources master repository
-is pulled explicitely to a local
-copy of the repository, which then may be used by e2.
-
-.SH "THE RELEASE"
-When software is developed and tested, a release needs to be built.
-This is done with the command \fBe2-build --release\fR.
-However, prior to building the release, all sources and the project
-information itself need to be tagged, to ensure reproducibility
-at a later time. Putting tags onto sources and the project is not
-a task of \fBe2\fR, but is in the scope of the source code management
-in use: First, put tags on all sources, that are kept in repositories.
-The tag names need not to be related to the release name, you may use
-different tag names for the different sources. Then, enter the tag names
-chosen into the appropriate source configuration files: Where the field
-\fBtag\fR is a list of tags, make sure the new tag will be the last in
-the list of tags. When done, commit and tag the project information
-itself. Here it is good practice to choose a tag name directly
-related to the release.
-
-To rebuild a release, that had been build a while ago, check out
-the project information: Fetch the version with the release tag on it.
-Now, you are ready to rebuild the tagged release.
-
-.SH "PROVIDING THE SOURCES"
-Sources, including a set of scripts to rebuild the project up to a certain
-result can be provided withing a result by enabling the collect_project
-flag in the result configuration.
-All files will be placed inside chroot for the build. The user will usually
-simply package the tree into a result file.
-
-.SH "SEE ALSO"
-.BR e2intro(7)
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
+++ /dev/null
-.\" Man page for <tool>
-.\"
-.\" (c)2007 emlix GmbH
-.\"
-.TH <tool> 1 "Dec 12, 2007" "2.1"
-
-.SH NAME
-<tool> \- <description>
-
-.SH SYNOPSIS
-<tool> [OPTION/PATH]...
-
-.SH DESCRIPTION
-\fB<tool>\fR blablabla.
-
-.SH RETURN VALUE
-Normally, exit status is 0. On error, it is non-zero.
-
-.SH OPTIONS
-.TP
-.BR \-\-help
-Show usage information.
-.P
-For further global options, see \fBe2intro\fR(7).
-
-.SH BUGS
-Doubtless there are many.
-
-.SH "SEE ALSO"
-.BR e2intro (7).
-
-.SH AUTHORS
-Gordon Hecker, Oskar Schirmer and Felix Winkelmann
-
-.SH COPYRIGHT
-(c)2007 emlix GmbH
projects / e2factory.git / commitdiff