search

genodelabs / goa

Tool for streamlining the development of Genode applications
GNU Affero General Public License v3.0
19 stars 18 forks source link

republishing an index projects should not necessitate a re-export of dependent projects #71

Closed jschlatow closed 5 months ago

jschlatow commented 6 months ago

Following the pattern of not overwriting existing depot content unless explicitly specified via --depot-overwrite, republishing an index project always requires --depot-overwrite. Currently, we propagate this switch when exporting dependent (Goa-managed) projects. This unnecessarily increases processing time and should be avoided.

jschlatow commented 6 months ago

Fixed by 83048e7

jschlatow commented 6 months ago

I just noted that, by not forcing the re-export of dependent projects, any change in architecture scope in an index project is left unnoticed by Goa. More precisely, if I have published an index in which a certain pkg was restricted to a particular architecture and later relax this restriction, Goa skips the export of the pkg because it is already present.

Commit 9213c0b fixes this by checking the depot dependencies of the pkg for every covered architecture.