Provde DEB packages

[seladb]

Related issue: #1498

This PR provides 3 DEV packages:

• Runtime - that includes only the shared libraries
• Developer - that includes static files, headers, cmake, pkg-config
• Examples - that includes the executable binaries of the examples

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.80%. Comparing base (08d661c) to head (0877c80).
⚠️ Report is 68 commits behind head on dev.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev    #2124      +/-   ##
==========================================
- Coverage   83.49%   79.80%   -3.69%     
==========================================
  Files         311      332      +21     
  Lines       54575    53521    -1054     
  Branches    11712    12246     +534     
==========================================
- Hits        45565    42715    -2850     
- Misses       7776     8447     +671     
- Partials     1234     2359    +1125     

Flag	Coverage Δ
23.11.6	7.29% <ø> (?)
24.11.5	7.33% <ø> (?)
25.11.1	7.34% <ø> (?)
alpine320	76.80% <ø> (+0.91%)	⬆️
fedora42	76.38% <ø> (+0.93%)	⬆️
macos-14	82.19% <ø> (+0.61%)	⬆️
macos-15	82.18% <ø> (+0.61%)	⬆️
mingw32	71.00% <ø> (+1.24%)	⬆️
mingw64	70.96% <ø> (+1.33%)	⬆️
npcap	?
rhel94	76.20% <ø> (+0.71%)	⬆️
ubuntu2004	?
ubuntu2004-zstd	?
ubuntu2204	76.21% <ø> (+0.78%)	⬆️
ubuntu2204-icpx	59.29% <ø> (+1.40%)	⬆️
ubuntu2404	76.52% <ø> (+0.99%)	⬆️
ubuntu2404-arm64	76.52% <ø> (+0.94%)	⬆️
ubuntu2604	76.44% <ø> (?)
unittest	79.80% <ø> (-3.69%)	⬇️
windows-2022	?
windows-2025	?
winpcap	?
xdp	53.05% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[clementperon]

@seladb maybe adding a CI test that install the .deb and build a project with it.
Remaining question is do we want to ship static libraries ? if yes it's a more complicated task i think

[seladb]

@seladb maybe adding a CI test that install the .deb and build a project with it. Remaining question is do we want to ship static libraries ? if yes it's a more complicated task i think

@clementperon I'll add CI to install the .deb packages.
I don't know how to create a .deb with static libraries, let's start with what we have and go from there...

[clementperon]

@seladb maybe adding a CI test that install the .deb and build a project with it. Remaining question is do we want to ship static libraries ? if yes it's a more complicated task i think

@clementperon I'll add CI to install the .deb packages. I don't know how to create a .deb with static libraries, let's start with what we have and go from there...

From my experience people that whant to have static libraries, they will locally clone and build the source of PcapPP
So I would tend to say everything that is shipped is shared libraries or source code nothing else

[seladb]

@clementperon I can't make updates to the PR, git says:

error: failed to push some refs to 'https://github.com/clementperon/PcapPlusPlus'
To https://github.com/clementperon/PcapPlusPlus
!	refs/heads/fork/clementperon/master:refs/heads/master	[remote rejected] (permission denied)