| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |/ /
| |
| |
| | |
Minor Changes
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| |\ \
| |/
|/| |
|
| | | |
|
| |\ \
| |/
|/|
| | |
master
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
Right now, as pointed out by swiftgeek on the issue tracker, it looks like a
spam site or placeholder site that is trying to sell something.
|
| |\ \ |
|
| | | | |
|
| |\ \ \ |
|
| | |/ / |
|
| |\ \ \
| |_|/
|/| | |
|
| | |/ |
|
| |\ \ |
|
| | | | |
|
| |/ /
| |
| |
| | |
it's for my company so no pull request needed
|
| |\ \ |
|
| | | |
| | |
| | |
| | | |
The extra newlines make actions with no output look strange.
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, the footer would not print if the project action failed
due to 'set -e' still being in effect (the subshell would return with
a non-zero exit code and exit immediately). The purpose of the
subshell for the project action is to better separate the execution
environment of the project from the library functions it
calls.
The test condition in the if-statement and its consequents were
changed in order to be more concise and informative.
|
| |\ \
| |/
|/| |
|
| |/
|
|
| |
This is the latest release of Fontconfig.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
project_blobs_ignore_path() prints nothing if a blobs-ignore file is
not found for the given project and arguments (if any); this behavior
should be the same for project_blobs_path()
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
This way we can be sure we're not attempting to build when instead
we should be bailing out (i.e. when the project's sources are
not available).
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The following will effectively disable any previous 'set -e':
foo_fail() {
(
set -e
false
true
)
}
if (set +e; foo_fail); then
echo "foo_fail() failed, unsuccessfully"
fi
Creating a subshell within an 'if' statement makes 'set -e'
non-functional.
|
| | |
| |
| |
| |
| |
| |
| | |
"update" actions were failing ever since revision b7fcc477 for
projects with git sources due to an error in
project_update_check_git() not returning 1 when it determined that the
project's sources was a git repo (to force an update, always).
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
The Libreboot build system is not fully automated, doesn't help with
the installation process per-se, and doesn't provide ROMs inside the
repository itself.
|
| |/ /
| |
| |
| |
| |
| | |
This fork of Paper is simply called the "Libreboot build system".
Addresses issue #613
|
| |\| |
|
| | |
| |
| |
| |
| | |
If the $install_path directory does not exist or a file which should
be present in the install directory isn't, fail.
|
| |/
|
|
|
| |
If the $build_path directory does not exist or a file which should be
present in the build directory isn't, fail.
|
| |\ |
|
| |/
|
|
|
|
|
|
|
| |
project_action_check() is there to avoid redundant actions from being
performed (e.g., if SeaBIOS is already built, don't build it
again). Since this is its primary purpose, we want to avoid erroring
out when it returns with a non-zero return code.
This addresses issue #614
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
If cd fails, nothing else should be done. This is to prevent a
potentially destructive action from being performed on the Libreboot
repository (if the script is executed from the same directory).
|
| | |
| |
| |
| |
| | |
Having a specific function for checking whether a patch would apply
isn't that useful if git_am and git_apply call it internally anyway.
|
| | |
| |
| |
| |
| |
| | |
git_diff_check() was added for future use since it's complementary to
git_diff_staged_check(). It could be used to check for a dirty
worktree, for example.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The recursive call in git_project_patch_recursive() is now performed
last so that if a patching attempt fails, the calling functions won't
attempt to apply more patches. The consequence of this change is that
patches are applied in (nearly) opposite order from before.
git_project_prepare_patch() is now called after
git_project_prepare_blobs() so that if patching fails and the user
chooses to perform additional project actions anyway, such as
building, the project is already deblobbed and not a risk to their
freedom. I had mistakenly reordered these function calls in a prior
commit.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Executing the project action within its own subshell makes it
easy to abort the action with a simple "exit" while still
allowing for the printing of the footer describing
failure/success. Prevously, if "exit" were called in a project
action the footer would not print.
|
| |\ \
| |/
|/| |
|
| | |
| |
| |
| |
| | |
The "let" builtin returns 1 if it's given an argument that evaluates
to zero.
|
| | | |
|
| |/ |
|
