Jean McCormack wrote: > Bug 5364 Example manifest should be organized for easy customization > > raises the issue that the manifests could be organized better to enable > people to more easily locate the few options that are likely to be modified. > > Here's my proposal: > > The areas that are hard to locate are in img_params so those are the > ones I'm > looking at moving. > > Current format: > img_params > packages > post_install_remove_packages > generate_ips_search_index > bootroot_contents > live-img_compression_type > build_area > grub_menu_modifications > output_image > finalizer > > > The issue is that bootroot_contents is so long that anything after it is > hard to find. > So what I think I'd like to do is move the small items to the top and > leave packages > and bootroot_contents near the bottom. Since the output_image/finalizer > scripts > are also largish I'll leave those last. > > Here's what I'm thinking > > img_params > build_area > live-img-compression_type > grub_men_modification > generate_ips_search_index > packages > post_install_remove_packages > bootroot_contents > output_image > finalizer > > Does this sound OK to everyone? >
I would think that package lists are much more likely to be modified than the compression and search index stuff. I'd move the bootroot compression setting right next to the packages. Also, I still suggest a signpost (as shown in my comments in the bug) to delineate the likely vs. unlikely modifications. Dave
