(mirror of https://github.com/vyos/vyos-live-build.git) https://git.amelek.net/vyos/vyos-live-build.git/atom?h=1.3.8 2017-09-01T08:22:09+00:00 2017-09-01T08:22:09+00:00 Matthijs Kooijman matthijs@stdin.nl 2017-08-28T09:29:54+00:00 urn:sha1:036b6161f250c0a798c987f0a6cf2ed9b987bd93 Since commit fdc9250bc (Changing package dependency checks within chroot to work outside as well), Check_package automatically checks for LB_BUILD_WITH_CHROOT and works inside as well as outside of the chroot, so no need to check LB_BUILD_WITH_CHROOT before calling them. Install_package and Remove_package are just a no-op when building without chroot, so they can also be called unconditionally. Restore_cache and Save_cache do not check LB_BUILD_WITH_CHROOT but it it should not hurt to call them when not needed (which already happened in some cases). This commit makes all Check_package calls unconditional on LB_BUILD_WITH_CHROOT. For binary_syslinux, this fixes the check (which used outdated paths outside the chroot since 7b6dfd9d1), for binary_grub-efi, binary_package-lists and chroot_package-lists this simplifies the code (but also causes the check to become package-based instead of file-based on apt-based systems), and for binary_loadlin and binary_win32-loader this adds the check outside the chroot which was previously missing. 2016-12-02T14:42:59+00:00 Raphaël Hertzog hertzog@debian.org 2016-12-02T14:42:59+00:00 urn:sha1:9c974b26bf532ba76f6d66423310f6d95b1ff1f7 2016-12-02T13:50:21+00:00 Raphaël Hertzog hertzog@debian.org 2016-11-29T17:18:01+00:00 urn:sha1:fb0d4e2a18746e817fa3d13f2ccc2f9788c65666 2016-07-31T13:08:11+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2016-01-18T03:07:48+00:00 urn:sha1:9d1a983cc8fe12966d1a2c24a6ee0cfb419b3ce5 * Added: functions/bootloaders.sh . This file adds bootloader functions that are heavily used in efi scenarios where a bootloader can act as a first or an extra bootloader. Since the introduction of the new switch: --bootloaders you can setup it like this: --bootloaders=syslinux,grub-efi . This means that syslinux is the first bootloader and grub-efi is the extra bootloader. * Added new bootloader functions: Check_Non_First_Bootloader and Check_Non_Extra_Bootloader. These functions let each one of the bootloaders abort the build because they cannot perform a role either as a first bootloader or as an extra bootloader. * Added bootloader functions: Check_First_Bootloader_Role, Check_Extra_Bootloader_Role and Check_Any_Bootloader_Role These functions let bootloaders to force their default role in a single line. At the same time many binary bootloaders were rewritten to make use of the new bootloader role functions explained above. These roles were enforced: binary_grub-legacy : First bootloader binary_grub-pc : Either first or extra bootloader binary_syslinux : Either first or extra bootloader If a bootloader is tried to be used in a role that it's not meant to be used then the build fails because that might lead to a non-bootable system. 2016-05-26T19:57:19+00:00 Kristian Klausen klausenbusk@hotmail.com 2016-05-26T19:41:48+00:00 urn:sha1:6b0777c53ea43096e978fc0ca7128108a7eb16f6 Closes: #818916 2015-08-29T21:56:41+00:00 Adrian Gibanel Lopez adrian.gibanel@btactic.com 2015-08-21T21:54:46+00:00 urn:sha1:d515ae56842f9420ff4c629eac18904f7beef2e8 Note: OLDIFS use makes IFS to be reset to "" instead to it being unset. Either we need to detect if old IFS was unset to unset it or we need a proper way of setting it as a local variable. Even more IFS it's not currently used in Check_package (which it's called from: binary_hdd). we should have a clean way of resetting/unsetting IFS when calling Check_package. The other approach it's to explicitly define IFS with its default value in the places inside live-build code where we implicitly suppose that it's going to have its default value. 2015-08-10T19:31:21+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-08-10T19:31:17+00:00 urn:sha1:421419c7fc96df18c422102a52879dd6860725a6 Unfortunately VERSION_ID on testing/unstable is currently not included in /etc/os-release, see #795124. 2015-05-03T13:50:03+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-05-03T13:49:57+00:00 urn:sha1:f93e83e351193a93c0a529798f7d01997c9d0909 Future live-build versions will still allow to use casper, but its configuration will be done differently by hooks in the config tree, rather than embedded and maintenance intensive code in live-build itself. 2015-01-04T19:05:44+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-01-04T19:05:39+00:00 urn:sha1:242aef5d8314a9b1da31e016f3329e6f04b8d675 2015-01-04T17:19:47+00:00 Daniel Baumann mail@daniel-baumann.ch 2015-01-04T17:08:09+00:00 urn:sha1:fdc9250bca7bfce660758d77af2ffa971bc19ecb