greg-minshall

i just ran into this (boiled down to the above ` $ cat`). i don't have any idea of all the ways the code might produce commands. but, the second...

in case anyone wants to experiment with this, here is a [patch](https://bin.disroot.org/?a378a7941a15c68b#782U8NTFvi4f5XwFg6nneMnaPfp5KpMt9GsnXhyHdJtp) for `--no-sync` (in `aur-sync`) and `--nodeps` (in `aur-sync` and `aur-build`). and here is the [`Makefile`](https://bin.disroot.org/?16a23a500996e096#2ngnadsAvh6hresr8YZtrjWdpvRZomjFvnLga7AYR6mx); it is just...

thanks for looking at this. one thing that maybe i didn't clearly explain: the intent is that (other than the messy step 3, building the `makedepends`) is that the steps...

here's some awk code. i was lazy and i didn't look at `aur-graph`, but just took the `--table` output from `aur-depends`. the code assigns a "level" number for each package:...

and, i will (hopefully) look at DAG.

btw, the above awk script leaves a few things to be desired. a script with fewer things left to be desired is available. one still unresolved issue is how to...

the maintainer of `gawk-xml` points out that in a `PKGBUILD` file, [`depends`](https://wiki.archlinux.org/title/PKGBUILD#Dependencies) lists any dependencies needed to *build* the package that are *also* needed to run the package (runtime dependencies)....

that sounds good. one point that maybe you already had in mind: > For each make/depends layer, build AUR packages, then install them (sudo pacman -S --asdeps) together with repo...

@Earnestly yes. the procedure i was thinking of is, for each "link" in the chain, do the non-sudo parts first (downloading, patching, building, installing in the local `aurutils` repository). then,...

@Earnestly indeed, i think, while not the *optimal* parallelization, one can run all the builds in a single `make/dependency layer` in parallel. cheers.