Skip to content
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

Address module reproducibility issues #1211

Merged
merged 1 commit into from
May 9, 2024

Conversation

dankm
Copy link
Contributor

@dankm dankm commented May 1, 2024

Use .PATH & bare filename. This prevents the real source path from being included in the built object, which improves reproducibility.

@dankm dankm force-pushed the dankm/module-path branch 2 times, most recently from da5a0e1 to c5333f4 Compare May 2, 2024 22:13
@igalic
Copy link
Contributor

igalic commented May 3, 2024

are these the only modules that use this pattern, or are you using them as an example?

@dankm
Copy link
Contributor Author

dankm commented May 3, 2024

are these the only modules that use this pattern, or are you using them as an example?

These are the only ones that I caught doing it. Most are doing it in a similar way to what I changed these to. Some are "building" the firmware by extracting a uuencoded file and then loading that. I searched for more, and didn't find any in-tree. Most look like this file in main.

Use .PATH & bare filename. This prevents the real source path from
being included in the built object, which improves reproducibility.

Signed-off-by: Dan McGregor <dan.mcgregor@usask.ca>
Reviewed by: imp
Pull Request: freebsd#1211
@bsdimp
Copy link
Member

bsdimp commented May 9, 2024

This builds, and produces what looks good. Should autoclose in a few minutes

@freebsd-git freebsd-git merged commit 8c2f6c3 into freebsd:main May 9, 2024
7 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants