Mercurial > crates > nonstick
diff libpam-sys/README.md @ 176:0730f5f2ee2a
Turn `libpam-sys-consts` back into `libpam-sys-impls`.
This moves the constants into `libpam-sys` and makes `libpam-sys-impls`
responsible solely for detecting the current PAM implementation.
| author | Paul Fisher <paul@pfish.zone> |
|---|---|
| date | Wed, 30 Jul 2025 17:53:31 -0400 |
| parents | 180237d0b498 |
| children |
line wrap: on
line diff
--- a/libpam-sys/README.md Wed Jul 30 14:57:12 2025 -0400 +++ b/libpam-sys/README.md Wed Jul 30 17:53:31 2025 -0400 @@ -13,7 +13,7 @@ This crate automatically chooses the appropriate PAM implementation you are most likely to need installed based on the target OS. You can also explicitly specify the PAM implementation you want (if not detected correctly) by setting the `LIBPAMSYS_IMPL` environment variable **at build time**. -All build-time configuration is performed by the build script of the [`libpam-sys-consts` crate](https://crates.io/crates/libpam-sys-consts). +All build-time configuration is performed by the build script of the [`libpam-sys-impls` crate](https://crates.io/crates/libpam-sys-impls). Normally, this crate exports all functionality available in the selected PAM library. `XSso` exports only the subset of the [X/SSO specification][xsso] supported by both OpenPAM and Sun PAM. @@ -43,7 +43,7 @@ fn some_func() { /* Linux-PAM / OpenPAM implementation */ } ``` -Further documentation on this is available in `libpam-sys-consts`. +Further documentation on this is available in `libpam-sys-impls`. ## Testing