| Age | Commit message (Collapse) | Author |
|---|
|
* Add --arch
* Default --dist and --arch from system
* Default --tag from --dist and --arch
|
|
|
|
This assumes that debootstrap treats empty string in the mirror argument
as no mirror argument being passed at all. We can be safe as long as the
runtime environment of debootstrap (i.e. the shell command language
interpreter) does not distinguish between the two cases outlined above.
|
|
Some packages have characters such as tilde (~) in their version
strings, which cannot be used inside Docker image tags.
See https://docs.docker.com/engine/reference/commandline/tag/
|
|
By default dpkg-buildpackage checks build dependencies and conflicts
before building the package, no matter whether source or binary. When no
.dsc file is supplied to the build command, baiji uses dpkg-buildpackage
to build a source package from the current directory first. This is
liable to fail if the host system doesn't satisfy the build
dependencies. Since the actual building job is done inside a Docker
environment, we don't need this behavior.
|
|
While executing the extract command, dpkg-source by default extracts the
source package to an output directory named as source-version. If the
source package format is 3.0 (quilt), the version string is taken from
the orig tarball, not the dsc file. Baiji attempts to use the
dsc version string, and fails if no correspondingly named output
directory is found after the extraction.
|
|
|
|
* Baiji can now generate source packages
* Baiji now uses a hash of the build dependency list to guess when it
should generate a new package-specific build image; the user can
override this guess with a command line argument.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Well, maybe. arrcus-sw runs to completion, anyway, good start.
|
|
|
|
|
|
|
|
|
|
|
|
|
