Date: Tue, 19 Mar 2024 08:23:06 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Alastair Hogge <agh@riseup.net> Cc: Freebsd Current <freebsd-current@freebsd.org> Subject: Re: sysutils/pam_xdg: Cancelled on -CURRENT Message-ID: <20240319082306.f4ffef050d8439be07b10962@bidouilliste.com> In-Reply-To: <4e4a5f033f4169dd07f4afdd7b5f6976@riseup.net> References: <4e4a5f033f4169dd07f4afdd7b5f6976@riseup.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, On Tue, 19 Mar 2024 06:54:27 +0000 Alastair Hogge <agh@riseup.net> wrote: > Hello, > > Recently a similar module (PAM) mentioned in the subject was committed > to base[1]. The module in base masks the currently installed Port, the > man page can be accessed with man -M /usr/local/share/man 8 pam_xdg, > however, I can now no longer build the Port. I noticed that the base > module has no WITHOUT_ option, tho, that might be extreme for one > module, but then again, the base module masks a more feature full > module. What is the practice to enable use of the Port again? At the > moment I am updating my host, and testing the following: > > diff --git a/lib/libpam/modules/modules.inc > b/lib/libpam/modules/modules.inc > index f3ab65333f4f..ddbb326f0312 100644 > --- a/lib/libpam/modules/modules.inc > +++ b/lib/libpam/modules/modules.inc > @@ -30,4 +30,3 @@ MODULES += pam_ssh > .endif > MODULES += pam_tacplus > MODULES += pam_unix > -MODULES += pam_xdg > \ No newline at end of file > > 1: > https://cgit.freebsd.org/src/commit/?id=6e69612d5df1c1d5bd86990ea4d9a170c030b292 > > Thanks. > I don't see why you can't build the ports. Using would be a problem but why do you want to use it now that we have one in base ? Do you have any problems with the one in base ? Cheers, -- Emmanuel Vadot <manu@bidouilliste.com> <manu@freebsd.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20240319082306.f4ffef050d8439be07b10962>