Replies: 2 comments 9 replies
-
I could add version files to the tree and update them with every new tag, if it can help you with packaging. |
Beta Was this translation helpful? Give feedback.
-
The current state (fc4990e) makes build nice and clean for me, i.e. I don't need any modifications on top the the snapshot of the source code from git, only the added But I envision that the taken approach may break for people who build the package from a git repo that is not a clone of the upstream, but repopulated/updated from a snapshot of the upstream code. They will get irrelevant version data. (Maybe there are no such people, and this is not a problem.) |
Beta Was this translation helpful? Give feedback.
-
We use debian as the base for our production systems, and I used to make
.deb
packages from previous versions of pyroute2 for internal use, when we could not afford to wait for the new version to arrive in debian. It used to be pretty straightforward.Now it's the first time that I need to do it again since the library was split in several parts. My old debianisation would not work, and I went upstream to borrow it from there. I found that they butchered
pr2modules/config/version.pyutil/update_version.py
, introduced build dependency on openstack(!) and use some openstack env variable to establish version. Basically, build-dependency on openstack prevents me from using this packaging configuration for our system.Still, there is a real pain point here: Makefile tries to make VERSION, and it requires one to build from live git repo. An "accepted" way to execute a (at least somewhat reproducible) package build is to have a clean source tree at the start (called
something_orig.tar.gz
in debian) withVERSION
andpyroute2.core/pr2modules/config/version.py
already created, thatmake
would not suddenly try to re-create.So, is there a way to produce a .git-free source tree (tar), that
VERSION
andpyroute2.core/pr2modules/config/version.py
If there is no procedure to do that, should it be introduced? Or am I missing the point altogether, and there is a different way to cleanly build packages?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions