hi, > Do I understand correctly that postinst touches /opt? Including /opt/bin? > I'm not sure that's a good idea even if that's only for migration (and > it's definitely a bad idea if anything in /opt is created on a clean > system). > As the maintainer script logic is very complex, please carefully test your > packgages with piuparts(1). > > *the old packages were installed into /opt, so postinst sets up symbolic > links in /opt to the new file locations Even if there was no old installation?
*yes, an existing customer may have hard-coded paths to the previous locations. A customer may install their software on a new 17.10 machine as a fresh install. > What are the binaries in src/build/install/resources/ext.tgz? Do they have > sources? > *they are some specially built utilities with no source. Non-free then. I also wonder how does that work with both ppc64 and ppc64el architectures. *this is a current exposure, which will be handled later. New source will be created and added. > Why are ${EXT_DIR}/ext.tgz and the firmware files unpacked on install and > not on build? > *the firmware files sum to ~60mb. They zip to ~40mb. We are trying to keep > the size of the pkg smaller. Don't you know packages are compressed? *previously, we were using fpm, which did not compress the packages. I can remove this. Regards, Mike Vageline IBM POWER Software Development