[arch-releng] archiso rebuild
Hello folks I asked this question on arch-general, but was referred here. Anyway, here's the original mail. ---------------------------------------------------------------------- I was wondering if there is a way to rebuild a custom live disc, using archiso, without having to download all the packages over again. The problem is that after making a few changes to the configuration, mainly inside root-image directory, i want to rebuild the iso. But, running build.sh says that everything is up-to-date. Alternatively, i tried removing the root squashfs file, and ran build.sh again. But, it started downloading ~500MB of packages all over again :( I'll probably have to do some more fine tuning before finalising the iso, and i don't want this to repeat itself. Please help. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
On 01/05/2012 04:27 AM, gt wrote:
Hello folks
I asked this question on arch-general, but was referred here. Anyway, here's the original mail.
----------------------------------------------------------------------
Hello!
I was wondering if there is a way to rebuild a custom live disc, using archiso, without having to download all the packages over again. If you talk about using existing ISO and rebuild them, the answer is no, at least not directly. You need to do things in manual way, and you need to understand how archiso works to unpack and re-create it. The problem is that after making a few changes to the configuration, mainly inside root-image directory, i want to rebuild the iso. What profile are you using?
are you talk about "source" root-image or "target" root-image (work/$arch/root-image)?
But, running build.sh says that everything is up-to-date. Alternatively, i tried removing the root squashfs file, and ran build.sh again. But, it started downloading ~500MB of packages all over again :(
When you want to repeat some step (functions in build.sh(, must remove the corresponding "lock" file inside "work/$arch/build.FUNCNAME".
I'll probably have to do some more fine tuning before finalising the iso, and i don't want this to repeat itself.
All customizations should go to build.sh:make_customize_root_image().
Please help.
I recommend to see how build.sh works from both profiles (baseline and releng). In baseline, this is the most simple way to build a new "archiso", second shows how official releng are build, customizing "root-image" and doing other things like splitting root-image.sfs, etc... -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
On Thu, Jan 05, 2012 at 11:09:16AM -0300, Gerardo Exequiel Pozzi wrote:
If you talk about using existing ISO and rebuild them, the answer is no, at least not directly. You need to do things in manual way, and you need to understand how archiso works to unpack and re-create it.
I mainly want that the packages ./build.sh downloads, are retained in a permanent cache. I am fine with rebuilding all the squashfs files, and not reusing the existing iso.
From what i see, after downloading and extracting the packages, build.sh removes the packages from the pacman cache directory.
Alternatively, can it use the chroot environment's pacman cache?
What profile are you using?
are you talk about "source" root-image or "target" root-image (work/$arch/root-image)?
I am using releng, and i'm talking about source root-image.
When you want to repeat some step (functions in build.sh(, must remove the corresponding "lock" file inside "work/$arch/build.FUNCNAME".
Will look into it, thanks.
All customizations should go to build.sh:make_customize_root_image().
Thanks, this also answered another question in my mind, that where does the arch user come from.
I recommend to see how build.sh works from both profiles (baseline and releng). In baseline, this is the most simple way to build a new "archiso", second shows how official releng are build, customizing "root-image" and doing other things like splitting root-image.sfs, etc...
I am using the releng method, as specified on the wiki. Maybe the wiki needs a bit of more detailed info. Thanks for all the explanation. -- O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
If you talk about using existing ISO and rebuild them, the answer is no, at least not directly. You need to do things in manual way, and you need to understand how archiso works to unpack and re-create it. I mainly want that the packages ./build.sh downloads, are retained in a
On Thu, Jan 05, 2012 at 11:09:16AM -0300, Gerardo Exequiel Pozzi wrote: permanent cache. I am fine with rebuilding all the squashfs files, and not reusing the existing iso.
From what i see, after downloading and extracting the packages, build.sh removes the packages from the pacman cache directory.
Alternatively, can it use the chroot environment's pacman cache?
On 01/05/2012 12:11 PM, gt wrote: pacman cache (from host) is used in chroot with a bind mount (when using mkarchroot). So for example, if you are building a 32-bit iso in 64-bit host, all 32-bit pkgs will be downloaded on /var/cache/pacman/pkg from host. Of course this is not an issue ;)
I am using the releng method, as specified on the wiki. Maybe the wiki needs a bit of more detailed info. Yes, contributions are welcomed :) Thanks for all the explanation.
Good Luck! -- Gerardo Exequiel Pozzi \cos^2\alpha + \sin^2\alpha = 1
participants (2)
-
Gerardo Exequiel Pozzi
-
gt