Replies: 1 comment 3 replies
-
|
I think reworking the workflows is a good idea, they aren't really doing what they should be doing right now I think. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The following are my proposed changes to the GitHub Actions workflow.
package.yml.archinstall-gitusing the commit that triggered it.iso-build.yamlto install archinstall as a package.archinstall-gitpackage from artifact.repo-add) and addarchinstall-gitpackage.pacman.confto use the local repo.archinstallwitharchinstall-gitinpackages.x86_64.This would have the added benefits of testing packaging, making the package available for download, and would better simulate the installation ISO environment for testing. The process outlined in the changes to
iso-build.yamlare derived from the ArchWiki. [1]The current process being used to build the ISO with the commit that triggered it has some weird side effects. For example opening
tmuxwhile in the ISO environment will re-trigger the archinstall installation process as will opening additional sessions.I wanted to bring this up for discussion because I am unsure if this change would be welcomed. It is possible the current method for installing archinstall into the testing ISO is more desirable for reasons that I am unaware of.
I build my own Archiso with archinstall installed as the package
archinstall-gitfor testing and it works fine. There is no issue in working with the project files either since they can be found at the path/usr/lib/python3.10/site-packages/archinstall/.@Torxed if you like the proposal I can put together a pull request.
[1] https://wiki.archlinux.org/title/Archiso#Custom_local_repository
Beta Was this translation helpful? Give feedback.
All reactions