Build order with dependencies #182
			
				
			
		
		
		
	
	
		Labels
		
	
	
	
	No Label
	
		
			
	
	
	
	Roadmap
		
			
	V
		
			
	bug
		
			
	docs
		
			
	duplicate
		
			
	enhancement
		
			
	good first issue
		
			
	help wanted
		
			
	idea
		
			
	invalid
		
			
	question
		
			
	wontfix
		
		
			
	Idea
		
			
	Roadmap
		
			
	bug
		
			
	duplicate
		
			
	enhancement
		
			
	help wanted
		
			
	invalid
		
			
	question
		
			
	wontfix
		
	
		No Milestone
		
			
		
	
	
		
		
		
			No project
			
				
			
		
	
	
	
	
	
		No Assignees
		
			
		
	
	
	
		1 Participants
		
	
	
		
		
			Notifications
			
				
			
		
	
	
	
	Due Date
	No due date set.
			
				Dependencies
				
				
		
	
	
	No dependencies set.
			Reference: vieter-v/vieter#182
			
		
	
		Loading…
	
		Reference in New Issue
	
	
	There is no content yet.
		
		Delete Branch "%!s(<nil>)"
	
	Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
An interesting problem arises when packages depend on other packages in the Vieter repository. The dependencies' builds should run before the package that it's dependent on to ensure they're both up to date. This would require us to know the order of the builds.
One idea would be to enforce having a .SRCINFO in the Git repo containing the PKGBUILD; the AUR does this as well. The cron server could then use this information to schedule the repositories accordingely. It would however require the cron server to clone all the repositories beforehand instead of during the build. I'm not also not sure what would need to happen if the dependency isn't scheduled for a rebuild yet.
Very interesting, in the compiler source code there's a dependency graph resolver that we could import.