Skip to content

Prefer system check which result in a new recipe should be treated as normal packages#919

Merged
ktf merged 2 commits intoalisw:masterfrom
ktf:pr919
Apr 14, 2025
Merged

Prefer system check which result in a new recipe should be treated as normal packages#919
ktf merged 2 commits intoalisw:masterfrom
ktf:pr919

Conversation

@ktf
Copy link
Copy Markdown
Member

@ktf ktf commented Apr 14, 2025

In general when are remote store is provided, we disable system packages. However, this
should not be the case if the system package results in a new recipe, because in that case
we consider the result of that recipe to be the package.

@ktf
Copy link
Copy Markdown
Member Author

ktf commented Apr 14, 2025

@davidrohr this is what we disucssed.
@singiamtel could you cross check the logic? The idea is that the system package replacements override the restriction on system packages when a remote store is specified (because in general we do not want to uploaded packages depending on the presence of system packages).

… normal packages

In general when are remote store is provided, we disable system packages. However, this
should not be the case if the system package results in a new recipe, because in that case
we consider the result of that recipe to be the package.
@ktf
Copy link
Copy Markdown
Member Author

ktf commented Apr 14, 2025

@singiamtel can we have a release with this?

@ktf ktf merged commit 25e30ae into alisw:master Apr 14, 2025
12 checks passed
@singiamtel
Copy link
Copy Markdown
Collaborator

LGTM. New release ongoing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants