4 ms·
The build server now needs the actual build dependencies instead of relying on pre-built intermediate build artifacts. This is a good thing, and should be expec
by kpcyrd 2y ago
The build server now needs the actual build dependencies instead of relying on pre-built intermediate build artifacts. This is a good thing, and should be expected from anything that claims to "build from source".
- carderne 2y agoI know it’s a good thing. I’m just curious to what degree packagers see this as extra work. Seems like probably not.
- vsl 2y agoIt's going to be a trivial amount of extra work. Packaging build systems (well, the mainstream ones: Debian, RPMs, ebuilds etc.) have the concept of runtime and build-time dependencies, so the maintainers will just need to add a few more packages to the build deps list.
- EuAndreh 2y agoIIRC Debian has a policy on preferring to generated files themselves. I couldn't find the link to it right now, though.
- EuAndreh 2y agos/generated/generate/
- pabs3 2y agoSome info on here: https://wiki.debian.org/AutoGeneratedFiles https://wiki.debian.org/AutoGeneratedFiles
- EuAndreh 2y agoYep, that says not to include generated files in VCS. I've also seen the bison and flex output included in VCS, and the same guidelines apply.
- bluGill 2y agoMany distributions have a policy of not using generated files, and more are implementing it after the xz hack. Most package systems have (not just Debian) have the concept of build and deploy dependencies. It is of course more work, and package systems tend to not be well documented and so it is hard to figure out, but it is possible: if you ask the experts they will help