ArduPilot Debian packaging
===========================

Dependency roles in the current SITL configuration
---------------------------------------------------

 * lwIP: excluded from source tree. Native-socket SITL does not require the
   stack; the Debian patch skips its sources and guards the options
   include. PPP and embedded Ethernet configurations need separate work.
 * littlefs: default SITL uses the POSIX backend. The Debian patch skips
   the littlefs build dependency unless --sitl-littlefs is selected.
   modules/littlefs is excluded from source tree.

Separately useful packaging candidates
---------------------------------------

[ ] littlefs: consider a general Debian development package. It is a small
    C filesystem library with upstream tests and a BSD-style licence.
    Determine whether the standard upstream version can replace the
    ArduPilot fork and how its compile-time configuration is exposed.
    This is not a prerequisite for the default POSIX-based SITL package.
[ ] Audit Waf's independent Python distribution and ArduPilot's fork.
    Establish a compatible packaged replacement and remove assumptions
    about modules/waf before dropping it from the source archive. Ensure
    the wrapper cannot fall back to fetching it with Git during a build.

Existing Debian dependencies and remaining integration work
-------------------------------------------------------------

[ ] Confirm the new libgtest-dev and python3-pymavlink integration through
    the full local and Salsa builds. Only the GoogleTest translation units
    should use C++17; vehicle code retains upstream's C++ standard.
[ ] If adding PPP or embedded Ethernet builds, assess liblwip-dev against
    ArduPilot's lwipopts.h and HAL integration. The native-socket SITL
    package needs neither bundled lwIP nor a liblwip-dev dependency.

Source retrieval and validation for the next repack
----------------------------------------------------

[ ] Prefer the upstream release tar.gz and fetch only indispensable extra
    source components. Avoid recursive retrieval of modules that will be
    discarded. The current selected-submodule watch arrangement is interim;
    MAVLink still recursively fetches pymavlink before Files-Excluded
    removes it from the source archive.
[ ] Keep watch, Files-Excluded and copyright coverage consistent with the
    actual new archive. Remove copyright stanzas only after their files
    have actually been removed from that archive.
[ ] Exercise uscan --force-download again after changing the retrieval
    arrangement. Inspect the archive for forbidden Python modules, unwanted
    optional modules and prebuilt firmware/libraries/plugins.
[ ] Build offline with only declared Debian build dependencies, checking
    that neither imports nor source-file dependencies fall back to bundled
    Python copies. Check the nocheck configuration as well.
[ ] Run the selected Vector2/Vector3 suites, all seven vehicle smoke tests,
    preset-default checks and disarmed Copter RC-input test. Full math
    death tests need a debug configuration; do not weaken their assertions.
[ ] Check installed launchers and the Salsa pipeline results before Debian
    upload. Physical-controller calibration, GUI operation and external
    simulator integration still need testing with the intended setup.

NEW review source-completeness follow-up
-----------------------------------------

[ ] Obtain the Cortex and ECU protocol XML inputs matching the ProtoGen output
    in libraries/AP_PiccoloCAN/piccolo_protocol. This release supplies only
    ESCVelocity_source.xml and Servo_source.xml. The directory's README names
    protocol_esc_velocity.xml, which is not present. Correct the regeneration
    instructions when the missing upstream definitions are available; do not
    claim that the complete protocol set can currently be regenerated.
