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

--nocheck not forwarded to makechrootpkg #1054

Closed
MithicSpirit opened this issue Oct 21, 2023 · 0 comments
Closed

--nocheck not forwarded to makechrootpkg #1054

MithicSpirit opened this issue Oct 21, 2023 · 0 comments

Comments

@MithicSpirit
Copy link
Contributor

Affected Version

67cc6f4 (and earlier)

Description

The mflags passed to makechrootpkg are determined at

let mut installer = Installer::new(config);
(the Installer constructor clones them from the current config.mflags). However, the CLI argument parser does not update config.mflags on --nocheck, and only sets config.no_check = true.
Arg::Long("nocheck") => self.no_check = true,
The config.mflags are only updated after the construction of the Chroot object (specifically, in build_pkgbuildsinstaller.installself.resolve_targetsresolver::flags), at which point changes to config.mflags do not propagate to the copy held by the Chroot object (which is what is used when running makepkg).

Fix

I think that the easiest way to fix this would be to hold the mflags in a single shared reference (Rc or Arc) so that updates to it from anywhere will propagate out to all other objects. Another (possibly more robust) option would be to make the build system more modular such that cloning these configurations is never even necessary, although I suspect that this would be a lot more work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant