02-20-2020, 05:47 AM
(This post was last modified: 02-20-2020, 06:08 AM by M@yeulC.
Edit Reason: add links
)
Just a few points regarding updates:
should be enough for updates, no need for images.
BUT, if you want to try out experimental (not yet merged) stuff, you can use images, or alternatively, compile and add the apk (alpine's equivalent of .deb) yourself.
To do so, use pmbootstrap build <name-of-the-package> with an updated aports (=package definition repository) folder (maybe make it track an experimental branch, or a merge request). pmbootstrap instructions are all over the web, but you can find some good ones on the postmarketos wiki. Or just follow the installation guide. We'd really need a page to explain this light maintenance.
Those "experimental" images mostly come from our aports merge requests, and might contain breaking changes. That said, you are welcome to try them out (using pmbootstrap is the preferred way) if you want to leave feedback on the merge request.
As all of this is quite experimental, don't expect to have a stable setup (calls working OOTB, etc) right now. When one is ready (a couple weeks, most likely), it will likely find its way quite quickly on the main postmarketos branch (so no need for images). Meanwhile, we will make sure to merge the better fixes in the package repository.
I am not sure what is the best dev strategy to adopt in the future, but if you want to help with development, ask those who are making progress if they need help testing stuff, and stick with it
Not sure there is a *lot* of value in image-hopping for now, for you or for devs. The issue with images is that they quickly become stale, though they are quite good as checkpoints, or if you want to flash a lot of devices.
Code:
apk update && apk upgrade -aBUT, if you want to try out experimental (not yet merged) stuff, you can use images, or alternatively, compile and add the apk (alpine's equivalent of .deb) yourself.
To do so, use pmbootstrap build <name-of-the-package> with an updated aports (=package definition repository) folder (maybe make it track an experimental branch, or a merge request). pmbootstrap instructions are all over the web, but you can find some good ones on the postmarketos wiki. Or just follow the installation guide. We'd really need a page to explain this light maintenance.
Those "experimental" images mostly come from our aports merge requests, and might contain breaking changes. That said, you are welcome to try them out (using pmbootstrap is the preferred way) if you want to leave feedback on the merge request.
As all of this is quite experimental, don't expect to have a stable setup (calls working OOTB, etc) right now. When one is ready (a couple weeks, most likely), it will likely find its way quite quickly on the main postmarketos branch (so no need for images). Meanwhile, we will make sure to merge the better fixes in the package repository.
I am not sure what is the best dev strategy to adopt in the future, but if you want to help with development, ask those who are making progress if they need help testing stuff, and stick with it
Not sure there is a *lot* of value in image-hopping for now, for you or for devs. The issue with images is that they quickly become stale, though they are quite good as checkpoints, or if you want to flash a lot of devices.