spin development: how to trust an iso built outside the fedora build sys

Hi there, I was wondering if there is any process that we (spin developers - music list) could use to confirm that a spin iso was 1. built with a particular kickstart file (or list of files when there is kickstart %include x directives). 2. hasn't been doctored on purpose eg by the person building

Re: spin development: how to trust an iso built outside the fedora build sys

On Sun, Aug 15, 2010 at 19:02:36 +1000, David Timms wrote: > > I was wondering if there is any process that we (spin developers - music > list) could use to confirm that a spin iso was > 1. built with a particular kickstart file (or list of files when there > is kickstart %include x directives)