Hi ede,
I do not know either. I suspect that living in /snap/bin/duplicity as a link
to /usr/bin/snap may be the only indicator.
It's possible that there are environment vars active when under snap. It's
hard to tell.
As for the snap itself,
* the python3 interpreter is included internally,
* is always Python 3,
* the shebang line is correct,
* script is marked executable.
If you absolutely must parse the command line, duplicity should reside at
//snap/duplicity/current/bin// along with python and python3 for the snap.
Snap runs first to set up a virtual env around that python3. Messing with that
could cause some real twitchy bugs that I would hate to chase.
BTW, this is how duplicity snaps run under Ubuntu 16.04. If it weren't for
Python 3 under snaps we'd be out of luck.
...Ken
On Sat, Jan 1, 2022 at 4:34 AM edgar.soldin--- via Duplicity-talk
<duplicity-talk@nongnu.org <mailto:duplicity-talk@nongnu.org>> wrote:
hey All,
i received bug report about duply vs. a snap packaged duplicity.
https://sourceforge.net/p/ftplicity/bugs/129/
<https://sourceforge.net/p/ftplicity/bugs/129/>
does anybody know a reliable way to detect that a binary is actually a snap
packaged version of the application?
i found that they are located under '/snap/bin/', but is this reliable,
meaning maybe configurable by some means?
thanks and Feliz Año Nuevo :).. ede/duply.net <http://duply.net>
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org <mailto:Duplicity-talk@nongnu.org>
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
<https://lists.nongnu.org/mailman/listinfo/duplicity-talk>
_______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk