Hi,

so is there any way around that. I don't want to have to multiply the
snaps for each subapplication. From a usesage perspective this pretty
much would be a show stopper to use snap over classical packages when
suddenly the same applications have to be called differently because
they have been installed as a snap and not as a deb.



On 29 July 2016 at 08:19, Didier Roche <[email protected]> wrote:
> Le 28/07/2016 à 20:01, Dietmar Winkler a écrit :
>
> Hi,
>
> I have one part that when compiled provides several binaries.
>
> See : https://github.com/dietmarw/snaps/blob/master/ipe/snapcraft.yaml#L50
>
> The problem is that the only "clean" bin binary is ipe all the other
> apps get installed as:
>
> $ ls /snap/bin/ipe*
> /snap/bin/ipe              /snap/bin/ipe.ipeextract  /snap/bin/ipe.ipescript
> /snap/bin/ipe.ipe6upgrade  /snap/bin/ipe.iperender   /snap/bin/ipe.ipetoipe
>
> So how can I avoid having to call the apps with "ipe." in front?
>
> Hey,
>
> This is the core part of the snapd design: commands are namespaced (with
> a default command shorten if app_name == snap_name).
>
> That way, you can avoid clash and conflicts when multiple snaps are
> installed on the system as they can't claim the same binary names,
> compared to a traditional packaging format.
>
>
> --
> Snapcraft mailing list
> [email protected]
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>



-- 
Dietmar Winkler, Assistant professor
University College of Southeast Norway
Faculty of Technology
Campus: Porsgrunn

http://me.dwe.no

Kjølnes ring 56, 3918 Porsgrunn, Norway

-- 
Snapcraft mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Reply via email to