Does the .AppImage use the native client or embed its own?

[RokeJulianLockhart]

.AppImages tend to include a darn lot (unnecessarily).

[bpozdena]

If you think somethings in the package are not necessary, which is definitely possible, please provide updated recipe for AppImage Builder.
Ensure to provide test results from at least 10 major Linux distributions to confirm you have not removed a dependency that does not ship with that particular distro.

[RokeJulianLockhart]

#137 (comment)

@bpozdena, I've no desire to modify the package, although I am thankful for the advice. I'd just like an answer to the question, especially so that I can accurately answer #138 (comment).

[abraunegg]

@RokeJulianLockhart
FYI - from reading a lot of your posts here and elsewhere, I find following your comments / posts / raising items then trying to link back - this all weaves at times a very difficult thread to follow at times. If you could perhaps tweak how you are raising items (issues, discussions and so on) that would be be potentially helpful.

... I'd just like an answer to the question, especially so that I can accurately answer ...

So I am going to assume here the question you are asking is this: Does the .AppImage use the native client or embed its own? (the topic title)

To the best of my knowledge, the GUI as per this GitHub repository (https://github.com/bpozdena/OneDriveGUI) - regardless of appimage or not uses the 'onedrive' client that I develop and maintain: https://github.com/abraunegg/onedrive underneath the GUI options.

This is really clear in the readme (https://github.com/bpozdena/OneDriveGUI#readme)

There is no native Microsoft provided Linux OneDrive Client.

[RokeJulianLockhart]

#137 (reply in thread)

@abraunegg,

1. To the best of my knowledge, the GUI as per this GitHub repository (bpozdena/OneDriveGUI) - regardless of appimage or not uses the 'onedrive' client that I develop and maintain: abraunegg/onedrive underneath the GUI options.

   There is no native Microsoft provided Linux OneDrive Client.

   I'm not asking whether it uses a different codebase - I'm asking whether a compiled binary of https://github.com/bpozdena/OneDriveGUI.git is statically linked inside https://github.com/bpozdena/OneDriveGUI/releases/download/v1.0.3/OneDriveGUI-1.0.3-x86_64.AppImage, or whether instead https://github.com/bpozdena/OneDriveGUI/releases/download/v1.0.3/OneDriveGUI-1.0.3-x86_64.AppImage uses $PATH like most distribution-native packages. I need to know in order to ascertain whether any configuration of https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64/onedrive-2.4.25-1.2.x86_64.rpm at /usr/bin/onedrive shall affect https://github.com/bpozdena/OneDriveGUI/releases/download/v1.0.3/OneDriveGUI-1.0.3-x86_64.AppImage at $HOME/Applications/OneDriveGUI-1.0.3-x86_64_2be1cb7745a73d7fb999ea3697c5048e.AppImage consequently. I ask this because similarly to https://github.com/flatpak/flatpak.git packages, https://github.com/AppImage/AppImageKit.git files frequently include their dependencies inside them.

2. FYI - from reading a lot of your posts here and elsewhere, I find following your comments / posts / raising items then trying to link back - this all weaves at times a very difficult thread to follow at times. If you could perhaps tweak how you are raising items (issues, discussions and so on) that would be be potentially helpful.

   You're, to my knowledge, the first person to mention that, so I've little context to go on - you'll need to be somewhat more specific for that to be actionable. Thanks though.