summaryrefslogtreecommitdiff
path: root/sbuild/sbuild-chroot-block-device-base.cc
AgeCommit message (Collapse)AuthorFilesLines
2013-04-02sbuild: Remove sbuild- prefixRoger Leigh1-135/+0
2013-03-31Update copyrights of all filesRoger Leigh1-1/+1
2013-01-05Replace tabs with spaces in all source codeRoger Leigh1-7/+7
2012-11-03sbuild::chroot: Add get_used_keys methodRoger Leigh1-4/+10
This splits out the used_keys functionality from set_keyfile. This is so that the keys used may be queried separately from keyfile loading.
2012-10-27sbuild: Test source session cloningRoger Leigh1-3/+0
2012-10-24sbuild: Don't call set_mount_device indirectly from ctorRoger Leigh1-15/+1
See #691376. sbuild::chroot_block_device_base::set_device was called from the chroot_block_device_base ctor, and called sbuild::chroot_facet_mountable::set_mount_device for all chroot types except lvm-snapshot. However, dynamic_cast<> fails during construction, leading to the mount device being overwritten, and --recover-session mounting the source LV rather than the snapshot LV. This patch moves the call to set_mount_device to the session clone operation in sbuild::chroot_facet_session_clonable, which is where the equivalent operation is done for lvm-snapshot. This is done prior to lvm-snapshot to ensure that the snapshot is not overwritten here either.
2010-07-11sbuild: Update doxygen commentsRoger Leigh1-8/+0
Also adjust sbuild::chroot_block_device_base to match the docs.
2010-07-11sbuild::chroot: Remove session_idRoger Leigh1-2/+2
This had exactly the same function as the chroot name, so merge into a single property.
2010-07-11sbuild: Remove unnecessary use of sbuild namespace qualifiersRoger Leigh1-1/+1
2009-12-13sbuild::chroot_block_device: Create session fileRoger Leigh1-69/+0
2009-12-12sbuild::chroot_block_device: Build correctly when LVM snapshot support is ↵Jonathan Callen1-0/+2
not available Signed-off-by: Roger Leigh <rleigh@debian.org>
2009-09-27sbuild: Validation of chroot properties allows strings to be emptyRoger Leigh1-1/+2
Before a chroot is fully initialised, it is possible for some properties to be empty strings. Don't fail in this case.
2009-08-10sbuild::chroot_block_device_base: Don't lock union block devicesJan-Marek Glogowski1-0/+14
Signed-off-by: Roger Leigh <rleigh@debian.org>
2009-07-30sbuild::chroot_mountable: Replace with chroot_facet_mountableRoger Leigh1-19/+23
2009-07-30sbuild::chroot_source: Reimplement as facetsRoger Leigh1-0/+8
Split into two facets, chroot_facet_source_clonable (for chroots providing clone_source functionality) and chroot_facet_source (for the resulting clone). This separation means that a single class doesn't need to cater for two essentially separate uses. The ability to list the installed facets, and name each facet for human consumption has been added.
2009-07-26sbuild::chroot: Pass chroot as parameter to facet functionsRoger Leigh1-14/+18
This is the first step to separating all derived chroot functionality such that it will not be derived from the sbuild::chroot class, but instead be contained within the chroot.
2009-07-20[sbuild::chroot] setup_env is constRoger Leigh1-1/+1
2009-07-04[sbuild::chroot_block_device_base] Simplify session flagsRoger Leigh1-1/+1
2009-06-30[sbuild::chroot:block_device] Split into block_device_baseRoger Leigh1-0/+190
In order to support union mounts on block devices, it can't conflict with the chroot_source support for lvm_snapshot. Therefore split into a base class, block_device_base, from which block_device and lvm_snapshot derive. Each can then implement chroot_source and/or chroot_union independently. block_device now has an explicit protected copy constructor for lvm_snapshot in order to allow its use as a source chroot type. This will prevent lvm_snapshot from gaining chroot_union support due to being directly derived from chroot_block_device.