| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
More generic, hopefully a bit clearer. The input must be a recipe, but
recipes depend on packages.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
* Only one recipe is investigated at a time.
* Output is hopefully closer to the desired format.
* Renamed the output file.
* Skip some basic native and virtual (cross-compilation) build tools so
that the output is not monstrously large.
|
|
|
|
|
| |
Use find_aktualizr_dependencies.sh to get the previous output for
aktualizr-related projects.
|
|
|
|
|
| |
There will not be recipes for those packages, so don't go looking for
them. We don't need them, anyway.
|
| |
|
| |
|
|
|
|
| |
Also expand/explain TODOs.
|
|
|
|
|
| |
It might be even better to get the path relative to the root of the repo
the files live in, but this is at least a step in the right direction.
|
|
|
|
|
|
|
| |
Not all possible dependencies are specified in DEPENDS, since we don't
build with everything enabled by default, so search for additional
potential dependencies explicitly. Also add a comment about the things
that we do not have visibility into from this process.
|
|
|
|
| |
Master branch returns empty instead of throwing an exception.
|
|
Finds aktualizr package information for OSS Review Toolkit.
|