Thanks for your reply.
Re:
Ø Looking at the postinst, it doesn't seem this is actually that you need to
execute any postinst in this specific case. The update-alternative calls here
are just to make available a default "traceroute" binary pointing to your
"usr/bin/traceroute.db" (same for manual page). You can expose it directly
through apps to get the same result:
apps:
traceroute:
command: $SNAP/usr/bin/traceroute.db
If the issue is that other commands from this package are using "traceroute"
internally, you can ship a symlink yourself that you ensure are in your $PATH
snap.
Yes I know I can do some special messing around to try and fix up the
installation but I don't think that is a good idea. How can I get the package
to install fully and correctly inside the SNAP, i.e. properly execute the
"postinst" commands.
If I install the package outside the SNAP using 'dpkg install' or 'apt-get
install' it properly installs on a UBUNTU system. What I'm looking for is the
mechanism to get the package installed inside the SNAP.
The current behavior just seems wrong to me. Are there any plans to fix it?
Thanks,
Dave
________________________________
DISCLAIMER:
This e-mail and any attachments to it may contain confidential and proprietary
material and is solely for the use of the intended recipient. Any review, use,
disclosure, distribution or copying of this transmittal is prohibited except by
or on behalf of the intended recipient. If you have received this transmittal
in error, please notify the sender and destroy this e-mail and any attachments
and all copies, whether electronic or printed.
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
