b9 0.2.3 → 0.2.4

raw patch · 2 files changed

+42/−9 lines, 2 filesPVP ok

version bump matches the API change (PVP)

API changes (from Hackage documentation)

Files

• README.md +2/−0
• b9.cabal +40/−9

@@ -2,6 +2,8 @@  [![Build Status](https://travis-ci.org/sheyll/b9-vm-image-builder.svg?branch=master)](https://travis-ci.org/sheyll/b9-vm-image-builder) +[![Hackage](https://img.shields.io/badge/hackage-B9-blue.svg?style=flat)](http://hackage.haskell.org/package/b9)+ Use B9 to compile your software into a deployable set of Linux-VM- or configuration images, from a set of scripts and input files and templates 

@@ -1,13 +1,44 @@ name:                b9-version:             0.2.3-synopsis:            A build tool and library for virtual machine images.-description:         Create, modify, use and share virtual machine images;-                     assemble and generate all associated files from templates.-                     All assembled files can be accessed by vm-build scripts as-                     shared directory in the build container, and/or-                     can be written to directories, ISO- or VFAT-images.-                     ISO/VFAT images are created so 'cloud-init' can recognize them.-                     VM-Build are executed in LXC containers managed through libvirt.+version:             0.2.4++synopsis:            A tool and library for building virtual machine images.++description:         Build virtual machine images for vm-deployments; resize,+                     un-partition, create from scratch or convert disk image+                     files in a variety of formats; assemble and generate all+                     associated files from templates and regular files.+++                     VM images can further be modifed through scripts, which are+                     executed in LXC containers into which the vm-images as well+                     as arbitrary directories from the host are mounted.+++                     All assembled files can also be accessed by vm build+                     scripts through a special directory mounted in the build+                     container, and/or can be written to directories, ISO- or+                     VFAT-images.+++                     The ISO/VFAT images that B9 creates are compatible to+                     'cloud-init's 'NoCloud' data source;+++                     B9 is also very well suited for compiling in a+                     containerized environment. For these applications, the+                     images can be marked as 'Transient' to indicate no further+                     interest in the VM-image itself, and B9 will discard them+                     after the build.+++                     B9 will never over-write source files, not even large+                     vm-image files - there is no intended way to modify a+                     source vm-image file 'in-place'.+++                     B9 operates in random build directories, which are+                     discarded when the build exists.+ license:             MIT license-file:        LICENSE author:              Sven Heyll <svh@posteo.de>