ALHP/ALHP.GO
6
34
Fork 9
Code Issues 30 Pull Requests Projects Releases Wiki Activity

Dependency aware package build order #78

New Issue
Closed
opened 2021-12-14 19:34:58 +01:00 by Eris420 · 5 comments
Eris420 commented 2021-12-14 19:34:58 +01:00
Copy Link

Currently it appears that there's no real handling of the order packages are built in. The impetus for this request is that currently there are updates available for many python packages that have been built with python 3.10, but the actual python 3.10 package is not yet available, so updating now would cause many python packages to break. It would be great if there was some sort of dependency awareness built in, so python 3.10 itself would be available before all the other packages that require it.

Currently it appears that there's no real handling of the order packages are built in. The impetus for this request is that currently there are updates available for many python packages that have been built with python 3.10, but the actual python 3.10 package is not yet available, so updating now would cause many python packages to break. It would be great if there was some sort of dependency awareness built in, so python 3.10 itself would be available before all the other packages that require it.
👍 1
burrhole commented 2021-12-14 23:16:54 +01:00
Copy Link

Maybe when a number of packages need to be rebuilt at once for the same reason, hold the packages from the repo until all of the queued builds complete? Probably not the smartest solution, but it seems like it could help.

Maybe when a number of packages need to be rebuilt at once for the same reason, hold the packages from the repo until all of the queued builds complete? Probably not the smartest solution, but it seems like it could help.
titaniumtown commented 2021-12-15 06:17:16 +01:00
Copy Link

omg, please! I've had to start using the main arch repos again because python packages are just all broken.

omg, please! I've had to start using the main arch repos again because python packages are just all broken.
anonfunc commented 2021-12-15 10:28:50 +01:00
Owner
Copy Link

I agree that this needs to be solved.

Maybe when a number of packages need to be rebuilt at once for the same reason, hold the packages from the repo until all of the queued builds complete? Probably not the smartest solution, but it seems like it could help.

That is probably the only solution which would not involve dependency resolving, which is not easily implemented. Maybe if there is something in libalmp that I could use, but I have to look that up.

The drawback here is that the whole repo would appear frozen for (in case of a rebuild in that magnitude we just saw) couple of days to a week.

I agree that this needs to be solved. > Maybe when a number of packages need to be rebuilt at once for the same reason, hold the packages from the repo until all of the queued builds complete? Probably not the smartest solution, but it seems like it could help. That is probably the only solution which would not involve dependency resolving, which is not easily implemented. Maybe if there is something in *libalmp* that I could use, but I have to look that up. The drawback here is that the whole repo would appear frozen for (in case of a rebuild in that magnitude we just saw) couple of days to a week.
anonfunc added the
enhancement
 label 2021-12-15 10:35:05 +01:00
anonfunc changed title from [enhancement] Dependency aware package build order to Dependency aware package build order 2021-12-31 12:14:52 +01:00
anonfunc commented 2022-01-21 15:29:28 +01:00
Owner
Copy Link

I forget to mention it here, but I implemented @burrhole 's suggestion in e0e76af757 a while back.

I would like a more sophisticated build-ordering at some point, but this prevents most of the problems for now, with the aforementioned drawback.

I forget to mention it here, but I implemented @burrhole 's suggestion in https://git.harting.dev/ALHP/ALHP.GO/commit/e0e76af757b6d21eb0ad89fa56036474b07f5d43 a while back. I would like a more sophisticated build-ordering at some point, but this prevents most of the problems for now, with the aforementioned drawback.
anonfunc commented 2023-06-03 14:05:08 +02:00
Owner
Copy Link

This is solved by building in batches.

This is solved by building in batches.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
blocked upstream

   
bug

Something is not working

  
build-failure

package build fails because of our added buildflags

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
informational

Provides information about something

  
invalid

Something is wrong

  
invalid/corrupt package

Package needs to be rebuild

  
packaging issue

   
priority: high

High priority

  
question

More information is needed

  
support

   
wontfix

This won't be fixed

No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
4 Participants
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: ALHP/ALHP.GO#78
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?