Closed RomanSaveljev closed 9 years ago
Thanks for this pull Roman. I was wondering why do we need to include this in the build process? I think it is possible to do something like:
junest -b
junest -f -- pacman -S package1 package2
Also I have just few minor concerns:
Hi,
Sorry, I was not clear about the motivation. I am using the junest image as a sandbox for embedded SW development. I would like to create as effortless installation as possible. The cross-dev environment needs kconfig-frontends. Maybe something else later. I am taking care about updates and distribution
I thought about doing it like you said, but is it possible then to easily re-package it and still have it clean?
These minor concerns are totally valid! I will rebase atop dev branch and also squash the commits.
Regards, Roman
Now you can pass the list of packages (groups) to junest build:
It should support both official distribution and AUR