Update README.md to include separately maintained junest build image

[srgk26]

Hi!

Recently, I noticed that the default build system provided in your URL seems outdated, in that it gives problems installing packages like vim. This problem was also raised in an issue #219. The problem is rectified when I build my own image using your instructions. I then created my own repo, uploading my own latest system build image so I could use it as needed. I will also be maintaining this repo from time to time.

I thought of somehow possibly including this in your project too, so new users without an existing Arch Linux system (therefore can't build their own system image), or simply to avoid the pain of building one themselves, can now use the images maintained in my repo.

I have updated your README to include this. I have also deleted the section using yaourt to install since yaourt is no longer in use in Arch Linux.

If you are happy with this change, or edit as you see fit, kindly accept the proposed changes.

[fsquillace]

Hi @srgk26 !

Thanks a lot for the help on this.

Unfortunately in the last period I have been very busy and could not dedicate enough time to this project. Nevertheless, I have just updated the JuNest image. I have an automated system which can build the image, validate it and upload to the repository for being consumed by everybody. The only problem for me is provisioning an ArchLinux machine which can run the script periodically and make the build ie. every week or month.
Cloud services do not support ArchLinux very well...

For now, what I would like to do is to manually run the script every 3 months to build the image (I will put a reminder for that).

For security concerns, I would like to make sure the content of the image is what is supposed to be and it must be validated.
Therefore, regarding your repository, I can put it as part of an unofficial section of JuNest images that people can consume at their own risk.

I hope you understand my concern on that.

Thanks again for the great work!
Filippo

[srgk26]

Hi @srgk26 !

Thanks a lot for the help on this.

Unfortunately in the last period I have been very busy and could not dedicate enough time to this project. Nevertheless, I have just updated the JuNest image. I have an automated system which can build the image, validate it and upload to the repository for being consumed by everybody. The only problem for me is provisioning an ArchLinux machine which can run the script periodically and make the build ie. every week or month.
Cloud services do not support ArchLinux very well...

For now, what I would like to do is to manually run the script every 3 months to build the image (I will put a reminder for that).

For security concerns, I would like to make sure the content of the image is what is supposed to be and it must be validated.
Therefore, regarding your repository, I can put it as part of an unofficial section of JuNest images that people can consume at their own risk.

I hope you understand my concern on that.

Thanks again for the great work!
Filippo

I understand! Just wanted to help. But thanks for updating it, I personally find junest useful when need to do something in HPC servers that would otherwise require root access, so thanks for junest!