aboutsummaryrefslogtreecommitdiff
path: root/nitrokey-sys/libnitrokey-v3.4.1/libnitrokey
diff options
context:
space:
mode:
authorDaniel Mueller <deso@posteo.net>2019-01-06 14:17:31 -0800
committerDaniel Mueller <deso@posteo.net>2019-01-06 14:17:31 -0800
commit0083f9dc7104dd21883451ad18c70758469ce1de (patch)
tree794a682bbd08804963d1d8662f3f0cf6ece0b5d1 /nitrokey-sys/libnitrokey-v3.4.1/libnitrokey
parent865f15edfdd7fca61b68da3c0aa3293dba630c81 (diff)
downloadnitrocli-0083f9dc7104dd21883451ad18c70758469ce1de.tar.gz
nitrocli-0083f9dc7104dd21883451ad18c70758469ce1de.tar.bz2
Use [patch] section to control local crate replacements
The nitrokey-sys crate poses a challenge in that upgrading it causes build errors caused by linking against the system's nitrokey library from multiple crates, which is not allowed. The exact cause of the problem is unclear but the suspicion is that a bug in Cargo's replacing logic is the cause of the issue. To work around this problem, this change switches to using the [patch] section for replacing crates with local copies instead of the [replace] one.
Diffstat (limited to 'nitrokey-sys/libnitrokey-v3.4.1/libnitrokey')
0 files changed, 0 insertions, 0 deletions