-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Keeping up to date #15
Comments
Well, i'm going to upload new releases with up-to-date packages at least once every two weeks (maybe even more often). Updating using pacman is not possible as the squashfs image inside Conty is read-only, so the only way to update it is to recreate it. This is how you can do this:
create-arch-bootstrap.sh will download the latest Arch boostrap and install/update all packages (you can even install your own set of packages if you edit the script). Root rights are required for this step. create-conty.sh will create a squashfs image from the boostrap obtained with the previous script and will create ready-to-use conty.sh. As a result, you will get Conty with updated packages inside it. p.s. These packages are required for the scripts to work properly: wget tar gzip squashfs-tools |
OK, that sounds good. Thanks. [edit] I just ran your instructions for creating a conty.sh, and the building & testing all went well. |
I'm using conty on Slackware64 to run Steam without having to convert to multilib. It works really well (including sound) and detected & used an attached PS3 controller, so all good. Thanks.
However I'm concerned about keeping conty's own software up to date. Since it's based on Arch Linux, I tried running
pacman
but that failed with:I guess while conty is under active development, I can just download the latest version whenever there's a new download. However they'll be fewer & fewer as everything becomes stable. Therefore, how to keep conty's built in packages up to date?
The text was updated successfully, but these errors were encountered: