-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ABI: Refactoring for libnetplan.so.1 #434
Conversation
fd4f857
to
89ebac9
Compare
The new systemd-dev build-dependency is not available on Jammy. But it is part of the 'systemd' B-D itself.
79baf2b
to
e6b3c7d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm! I just left 2 non-blocking comments.
Oh, about the Network Manager tests. I'm not sure why they are failing :( I tried it locally with netplan.io from -proposed and systemd from release (253) they just work... not sure if it's related to the usrmerge stuff... |
wait... we got rid of the old .0 shared library, Network Manager needs to be rebuilt on Noble to work properly. |
Ahh, yes! That might be it. On the distro side this will be enforced by changing the |
1e8a30b
to
13b067c
Compare
Also re-build the NetworkManager package during test, to account for the new libnetplan.so.1 shared object.
They are now all encapsulated inside the netplan_state struct, to be used through the API. Also, restructure the generator's includes for better separation of public vs internal headers.
Description
Please review commit-by-commit.
Bumping libnetplan's SOVERSION to 1, indicating breaking changes. Also, bumping Netplan's version to "1.0" already, in preparation for the next release.
I've dropped some more legacy code and cleaned up the existing public & internal APIs, making sure we do not export anything that is either prefixed with
_netplan_
(internal API) ornetplan_
(public API).Note
Feel free to ignore the last (big) commit in "abi-compat", as that is auto-generated (e6b3c7d)
Known issues
One thing I noticed already is, that it is building against
noble-release
using systemd v253 (instead of v255 from -proposed), therefore getting the wrong systemd-generator path frompkgconf
.FR-3760
Checklist
make check
successfully.make check-coverage
).