Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
explicitly specified
Now, if configuration is not specified for a system dependency package, then
it is assumed to be specified for all current configurations and their
explicitly linked configurations, recursively, including private
configurations that can potentially be created during this run.
|
|
|
|
|
|
then from just main database
|
|
|
|
|
|
|
|
Now that a package name can include a configuration, using just spaces is
insufficient.
|
|
|
|
|
|
|
|
case-insensitively on Windows
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also document tests, examples, and benchmarks package manifest values.
|
|
|
|
|
|
|
|
Also fix some tests to properly work if the project path contain spaces.
|
|
variants for clarity
|
|
testscript commands
|
|
|
|
pkg-build
|
|
|
|
|
|
|
|
|
|
We used to also fail when downgrading non-system dependencies. Now we warn
when up/down-grading package-held dependencies, instead.
|
|
|
|
|
|
|
|
|