-
Notifications
You must be signed in to change notification settings - Fork 18
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
Remove BUILD_DEB option #125
Conversation
This feature allows building a Debian package that can run on a desktop machine as a kind of simulation mode. I'm not aware of anyone using this: real usages build using Yocto or run locally in development. Remove this feature.
We maintain a Debian package here https://github.com/torizon/aktualizr-deb (for torizon-aktualizr, but it's pretty much the same thing). Should anyone need it, it should be trivial to make it point to the upstream repo instead. |
I wasn't aware of that--if people are using it then how about bringing that upstream? The delta looks pretty minimal |
I think all the packaging changes are self-contained in the |
Are you using the Debian packing tooling rather than cpack on your branch @leonheldattoradex? If so, then I'm even more keen to nuke the stuff that is using |
Yes, we have a custom pipeline that uses the usual tools[0]. One can just [0] https://github.com/torizon/torizon-deb-ci I'll setup a build for the "non-Torizon" Aktualizr and create an official Debian package on the upstream, what you think? |
I imagine the existing solution using @cajun-rat Now that we know someone is, shouldn't we keep it? Or does it add some relevant maintenance effort? Replacing the @leonheldattoradex Or are there good reasons for using the Debian tools rather than |
It depends what you mean by 'works' :) Running
The current situation as I see it is we have 2 independent implementations of similar functionality:
Since @leonheldattoradex is the active maintainer here, I'll let them pick the implementation approach. I recall the Debian community prefers to use Debian tooling to build packages rather than those built into other tools, so while cpack is good for people who are doing 'cmake' it is worse for people doing 'Debian'. I think there are two approaches from where we are today:
My preference would be for the first, but if someone wants to work on the latter I'm happy to help! |
Ok, considering the above, it seems reasonable to nuke |
Cool. I'll merge this now. Shout if I can help with the upstreamng bit! |
This feature allows building a Debian package that can run on a desktop machine as a kind of simulation mode. I'm not aware of anyone using this: real usages build using Yocto or run locally in development. Remove this feature.