Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sketching out a community & patch-based approach for adding extra features #94

Closed
xynydev opened this issue Jun 1, 2023 · 1 comment

Comments

@xynydev
Copy link
Member

xynydev commented Jun 1, 2023

I think it would be beneficial to have some kind of official and documented way of adding "extensions" or "patches" to startingpoint-based images / repos.

Having the scripts functionality, it would be entirely possible to boostrap that for such a feature. The scripts already have access to the recipe (where they could read their configuration, maybe from under a separate namespace like unofficial:).
It would be pretty easy to have a system where; Oh you want libvirt and virt-manager? Well this guy maintains a set of packages for that that you can just pull in like this.

The question is, what is the mechanism for pulling it in. There could be an extra option, like extrarepos: that just downloads scripts for you, or the scripts could just be added manually.

@xynydev
Copy link
Member Author

xynydev commented Jun 30, 2023

We have ublue-os/bling now, where extra "bling" should be added and maintained, then pulled in here. Possible community endeavours would probably go via a similar route, COPYing stuff between containerfiles, RPMs, and so forth. Scripts can easily add new sections to recipe.yml, and scripts can be easily COPYed around.

@xynydev xynydev closed this as completed Jun 30, 2023
RoyalOughtness referenced this issue in secureblue/secureblue Nov 27, 2023
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

No branches or pull requests

1 participant