The library ldap3(dependency) use patch.crates-io section to overwrite one of
the crate's location. However, we use patch section also to change the
remote crate to local store one. We cannot patch a patch in cargo.
There is a workaround now by clone the repo manually and modify the
patch section in the Cargo.toml to our manually clone one.
Details
Details
Diff Detail
Diff Detail
- Repository
- R11 FreeBSD ports repository
- Lint
No Lint Coverage - Unit
No Test Coverage - Build Status
Buildable 63694 Build 60578: arc lint + arc unit
Event Timeline
| net/lldap/Makefile | ||
|---|---|---|
| 31 | How about using ldap:ldap ? | |
| 42 | Use ${MKDIR} | |
| 44 | Use ${INSTALL_SCRIPT} for copy and chmod in the same time. | |
| 45 | See if ${COPYTREE_SHARE} is suitable here. | |
| 46 | Use ${CP} | |
| net/lldap/pkg-descr | ||
| 4 | superfluous white line. | |
| net/lldap/pkg-plist | ||
| 8 | if we change USER/GROUP, these two lines also need change. | |
| 24 | superfluous white line. | |
Comment Actions
@yuri Hello, I notice that you are the author of wasm-pack. The lldap project use wasm-pack to build their frontend code.
A question is that wasm-pack will download wasm-bindgen-cli at the first time when it try to build the project. The installation of wasm-bindgen-cli is hardcoded in the wasm-pack code. See: https://github.com/rustwasm/wasm-pack/blob/32e52ca893e26c97bbf478c57ae1e9abed23c449/src/command/build.rs#L419. And the version should be matched strictly. Thus wasm-bindgen-cli will not compile and install before we build the project. Then when we try to build frontend code by wasm-pack, it failed to download wasm-bindgen-cli as we are not allow to do so in poudriere. Do you have any recommended way to archieve this?