Mercurial > crates > nonstick
diff src/lib.rs @ 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 | e30775c80b49 |
| children | 4f46681b3f54 |
line wrap: on
line diff
--- a/src/lib.rs Wed Jul 30 14:57:12 2025 -0400 +++ b/src/lib.rs Wed Jul 30 17:53:31 2025 -0400 @@ -83,7 +83,6 @@ //! the address space of the calling application. To implement a module, //! create a `dylib` crate and implement a [`PamModule`], and export it //! using the [`pam_export!`] macro. -//! //! ```toml //! ## Your Cargo.toml //! [package] @@ -93,7 +92,6 @@ //! [lib] //! crate-type = ["cdylib"] //! ``` -//! //! ``` //! // Your lib.rs //! @@ -127,7 +125,7 @@ //! // features. //! } //! ``` -//! +//! //! This gets built into a library like `pam_samename.so`. By installing this //! into your PAM library directory and configuring PAM to use it in //! the authentication stack (beyond the scope of this documentation), it will @@ -158,6 +156,7 @@ //! - [OpenPAM admin documentation][bsdpam8] //! - [Illumos pam.conf documentation][sunpam5] //! - [The original PAM specification][spec] (mostly of historical interest) +#![doc = ""] #![doc = crate::_doc::man7!(man7pam8: 8 pam)] #![doc = crate::_doc::manbsd!(bsdpam8: 8 pam)] #![doc = crate::_doc::mansun!(sunpam5: 5 "pam.conf")] @@ -218,4 +217,4 @@ handle::{ModuleClient, PamShared, Transaction}, module::PamModule, }; -use libpam_sys_consts::pam_impl_name; +use libpam_sys_impls::pam_impl_name;