Skip to content

Conversation

@silentjet
Copy link

No description provided.

@silentjet silentjet force-pushed the add_debian_package_files branch 2 times, most recently from 2fe7dc8 to ceae627 Compare March 9, 2024 14:41
@silentjet
Copy link
Author

Hi @peterbarker
Thanks for your review. Was busy for quite some time. I'll update it and will upload a clean version. This one is quite made-on-knees, thus dirty (and that's why WIP is here).

@silentjet silentjet force-pushed the add_debian_package_files branch from ceae627 to 3dcceec Compare August 1, 2024 09:36
@silentjet
Copy link
Author

Hi @peterbarker
Sorry for such a delay, I worked through the actual build and runtime dependencies, and now they are real and validated.
please review.
building the package can be performed using a command:

dpkg-buildpackage -b -us -uc

resulting debian package can be installed using dpkg tool:

dpkg -i ../python3-pymavlink_2.4.41_amd64.deb

@silentjet silentjet changed the title WIP: Add debian package files Add debian package files Aug 1, 2024
@tpwrules
Copy link
Contributor

tpwrules commented Jun 28, 2025

Could you help me understand why this would be included here instead of in Debian's repos?

@silentjet
Copy link
Author

silentjet commented Jul 1, 2025

pymavlink is not a part of Debian official repositories. And adding a new packages not an easy task (as well as later maintaining it). Saying that, as a debian/ubuntu user I faced multiple issues in my "daily" use, which are related to pymavlink itself:

  • installing the package "manually" requires use of venv since debian12 and ubuntu 22.04, - can I overcome it? yes, but this is unsecure and system wide approach which is not so good in general
  • installing the package from pip is also bit complicated causing problems on different platforms and python versions, can I overcome it - technically yes, the same as above.
  • installed package requires adding some "home bin" directory (depends on the system, but mostly $HOME/bin), - that is rather an unsecure approach, and while it is totally acceptable, still it is an unsecure one.

Thus, the 3rd party built package is giving a way to solve most of these problems and is extremaly useful if containers are used (installing a debian binary package is so much faster then every time build/deploy on vm)

@silentjet silentjet force-pushed the add_debian_package_files branch from 3dcceec to f6c3b0a Compare September 2, 2025 09:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants