Closed peppidesu closed 1 year ago
Cargo.lock
being out of date is a problem in and of itself, and the package should ideally always be built according to the lockfile. So I don't consider that to really be a problem.
The PKGBUILD will not touch user specific files, nor should it ever do that. PKGBUILDs are supposed to build the package, and user specific config files are not a part of the package.
There are some issues with the AUR package at the moment:
The
--frozen
flag can cause the build to fail. Consider removing it or making sure cargo.lock and cache are updated before build in the PKGBUILD.The PKGBUILD currently does not copy the config from
/etc
to~/.config
.