[arch-releng] Update needed to releng scripts

[Gerardo Exequiel Pozzi]

On 06/17/2011 06:02 PM, Dieter Plaetinck wrote:
> On Thu, 16 Jun 2011 20:40:02 -0300
> Gerardo Exequiel Pozzi<vmlinuz386 at yahoo.com.ar>  wrote:
>
>> Hello Dieter
>>
>> I want some coordination with you to merge my dm-snapshot branch in
>> master (archiso) so you can change releng scripts.
>>
>> Detailed manually build steps are here [#1]
>>
>> If you need more info please let me know.
>>
>> Basically the changes are (from build view):
>>
>> ---- Single ISOs ----
>> * Deprecated configs/syslinux-iso in favour to configs/releng
>> * configs/releng uses a bash script instead of make
>> * Equivalence of commands is:
>>
>>       make net-iso ->  ./build.sh net_iso_single
>>       make core-iso ->  ./build.sh core_iso_single
>>       make [all] ->  ./build.sh all_iso_single
>>       make clean ->  ./build.sh clean_single
>>
>> * Note: Like with previous method, after building "core", if you build
>> "netinstall" you get a "core" iso called "netinstall". (TODO: I need to
>> fix this in a easy way)
>> * Important: inside the chroot you need one loopback device available (@1)
>>
>> ---- Dual ISOs ----
>> * Deprecated archiso2dual script in favour of configs/releng/build.sh
>> * While archiso2dual use *.iso images, build.sh use the result of
>> ./build.sh *_iso_single commands, in other words join
>> ${work_dir}/${arch}/iso (via hardlinks).
>> * No more profiles (single, split, full), since the work of profile
>> "split" is now done for single images.
>> * build.sh accept these commands for doing dual images.
>>
>>       ./build.sh net_iso_dual
>>       ./build.sh core_iso_dual
>>       ./build.sh all_iso_dual
>>       ./build.sh clean_dual
>>
>> * These commands does not trigger the build of single images. You need
>> to do it before.
>> * No issues if execute first "core" then "netinstall" (I managed it in
>> this case)
>> * No loopback device is needed for this step.
>>
>>
>> (@1) Create one, for example "mknod /dev/loop1032 b 7 1032" for 32 bit
>> chroot and loop1064 for 64 bits (of course this will work only if loop
>> module is loaded without any parameters that limit the number of loop
>> devices or set number of partitions).
>>
>> [#1] https://wiki.archlinux.org/index.php/User:Djgera#archiso
>>
> Well, once you merge this into archiso I will temporarily disable the automatic creation of images, hack
> http://projects.archlinux.org/users/dieter/releng.git/ until it works, and reenable automatic creation.
OK.
> But yeah, first make sure that 'core' images are really core and 'netinstall' are netinstall.
Not a big issue. This is the same bahaviour like with previous build 
system. Since you not have any issue before, do not worry about that now.
> What's the way to just create all images?
> ./build.sh all_iso_single&&  ./build.sh all_iso_dual ?
>
Better explained in the wiki.

1) share a common directory between two chroots (32 and 64 bits) for 
working directory.
2) execute in 32 bits chroot: ./build.sh all_iso_single
3) execute in 64 bits chroot: ./build.sh all_iso_single
4) execute in any chroot (don't care) : ./build.sh all_iso_dual

Steps 2 and 3 require one available loopback device in the chroot.
Step 4 do not require loopback devices like with archiso2dual.

> Dieter
>

-- 
Gerardo Exequiel Pozzi
\cos^2\alpha + \sin^2\alpha = 1