| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
| |
We don't do releases, so having the version number in the source is
misleading. If and when we start doing numbered releases, it's easy
to add back. However, YAGNI and all that.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Also, change builder.py to always obey the --max-jobs setting, unless
a morphology has a max-jobs field.
The defaults have been chosen so that they work for everyone equally
well. It may be useful to have a local mirror and then set the options
to point there, but it's not reasonable to try to guess such things,
so the defaults can be adapated to that.
Collect the defaults into one place so they're easier to overview.
The cliapp interface for adding settings is verbose enough that the
defaults were getting buried.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This we a proof-of-concept, and we want to explore various options of
how to do this, so let's not keep the code in morph. The code also has
no tests, so it is already likely to have bit-rotted.
If we decide we want to, we can always resurrect it from git history.
|
|
|
|
|
| |
This avoids problems with files with the right names but partial
content, if morph is killed in the middle of writing the file.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it easier to check the output with vgrep for errors or
problems. Voluminous git output made that hard.
The key is that "git bundle create" has no --quiet optio (meh),
so we have to redirect stderr to /dev/null. However, that would
hide real errors, which we want to catch. Luckily, we can just
replace the call to subprocess.call with a call to
subprocess.check_call, and then we'll at least abort if there's
an error, instead of silently ignoring it.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Either all .gits need to be left alone, including submodules, or
all of them get changed.
Doing all gets surprisingly complicated, as bottom-up traversal is
needed for directories to have their mtimes set, which means that
either we check the path for a .git component, or we do our own
traversal function, to top-down exclude .git and bottom-up set
mtimes.
This is more effort than it is worth when git probably doesn't care
so let's just drop it entirely.
|
| |
|
|
|
|
|
|
|
|
| |
Setting mtimes can fail if it is a symbolic link and it
points to a non-existant file.
This has happened when we had symbolic links pointing to files
in a submodule, so we set mtimes after submodules have been
checked out.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
This is a bit stupid and requires tests to be adjusted (which is done in
this commit as well).
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
| |
This is done to keep the git repository intact with history and all
that. cp + checkout turns out to be faster than a regular "git clone".
In order to avoid roundtrips to the internet whenever a chunk tries to
do something with submodules, we force the submodule URLs to point to
our locally cached repos.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Putting the commands in a file made it more difficult to tell
what happened in scripts, until the self.msg was added.
After then it made the commands more difficult to reproduce
So if it can safely be done in a single command it should be more
readable.
This approach uses sh -c to cd then evaluate the remaining options
The command is 'cd "$1" && shift && eval "$@"', then passes the command
as arguments to the shell script, so the program does not need to do any
escaping of strings.
If the commands were a list of strings instead of a quoted string then
it would be a bit safer, but less flexible for use.
|
|
|
|
|
|
|
| |
This is done to not print confusing errors in situations where one of
the bundles or base URLs works and everything is fine. If all of them
are failing though, we now print all the error messages in order to give
users an overview over what might have gone wrong.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Otherwise we have to deal with git's not liking colons in filenames.
|
| |
| |
| |
| | |
Now it should actually work.
|
|/
|
|
|
|
| |
This adds options --staging-filler and --staging-chroot.
The wisdom of these options needs to be re-considered at
some point, but for now they're OK.
|
|
|
|
|
| |
This time, with testing. For a five line method, this was surprisingly
tricky to get right. Should sleep properly at night...
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to do this:
"build-system": "autotools",
"configure-commands": [
"./configure --prefix=$PREFIX --disable-nls --enable-foo"
]
The explicit command is used for configure, but the commands provided
by the autotools build-system will be used for build-commands,
test-commands, and install-commands.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is almost as good as --bare. But unlike --bare, it properly sets up
the 'origin' remote and creates the 'refs/remotes/origin/...' branches.
When cloning with --bare, and you end up with "refs/heads/master", not
"/refs/remotes/origin/master". You can re-add the remote 'origin', still
no "refs/remotes/origin/master". Only after you update the remote (after
re-adding it), the bare clone has "refs/remotes/origin/master"... and a
"refs/heads/master" that is out of sync. An ugly mix, basically.
So maybe this approach is better.
|
|
|
|
| |
This reverts commit 63cab3e0e2f550a0bfe470d018063a8b91a759bd.
|
|
|
|
| |
This reverts commit e0fb97f08156af97ec2341ec8061fe514ae358e5.
|
|
|
|
|
|
| |
This is needed because if there are any connection errors during
bootstrap, we do not want that to affect the build. It is mostly a hack
that should not be necessary. But it is and that's life.
|
| |
|
| |
|
|
|
|
| |
This order makes most sense in all regards.
|
| |
|
|
|
|
| |
This is to improve logging, error reporting and readability of the code.
|
| |
|
|
|
|
|
|
|
| |
If the SourceManager is told to not update repositories, then it should
always assume that we have the repo cached for at least one of the base
URLs. In that case it should never try to download a bundle from a
bundle server and just skip all bundles.
|