gxpkg misplans downstream rebuilds #590

Open
opened 2021-01-13 17:44:46 +00:00 by fare · 3 comments
fare commented 2021-01-13 17:44:46 +00:00 (Migrated from github.com)

When a package foo is rebuilt by gxpkg, gxpkg automatically rebuilds all packages that depend on foo. Unhappily, it doesn't do it in a correct order such that if baz depends on bar that depends or foo, bar will be rebuilt before baz, and other dependencies of bar will be rebuilt if necessary.

Fix gxpkg to either do the right thing or not try to do too much and fail.

When a package foo is rebuilt by gxpkg, gxpkg automatically rebuilds all packages that depend on foo. Unhappily, it doesn't do it in a correct order such that if baz depends on bar that depends or foo, bar will be rebuilt before baz, and other dependencies of bar will be rebuilt if necessary. Fix gxpkg to either do the right thing or not try to do too much and fail.
fare commented 2021-06-08 21:17:33 +00:00 (Migrated from github.com)

Note that :std/misc/concurrent-plan can help do the parallel (or then again sequential) execution of a topologically sorted plan, whereas :std/make contains an example of a topological sort algorithm that could be adapted (or factored out?) to handle builds at the inter-package granularity as well as at the intra-package granularity.

Note that `:std/misc/concurrent-plan` can help do the parallel (or then again sequential) execution of a topologically sorted plan, whereas `:std/make` contains an example of a topological sort algorithm that could be adapted (or factored out?) to handle builds at the inter-package granularity as well as at the intra-package granularity.
vyzo commented 2023-09-22 11:59:56 +00:00 (Migrated from github.com)

Can we get this fixed soonish?

Can we get this fixed soonish?
vyzo commented 2024-12-14 01:22:50 +00:00 (Migrated from github.com)

Is this still an issue?
I think it has been fixed with the nrw build planner for parallelization.

Is this still an issue? I think it has been fixed with the nrw build planner for parallelization.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
mighty-gerbils/gerbil#590
No description provided.