On Wed, Aug 23, 2017 at 02:24:37PM +0000, Michael P Vageline wrote: > > 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. There is no specific restriction on touching /opt by packages but generally we don't do that. Note though that there is "Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator." which may or may not apply here. > > 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. Will that also apply to the firmware? And what about the click-through license? -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature