Re: sysutils/pam_xdg: Cancelled on -CURRENT

On 2024-03-19 15:23, Emmanuel Vadot wrote:
> Hi,

Hey Emmanuel,

> 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.

From sysutils/pam_xdg[2]:

.if exists(/usr/lib/pam_xdg.so)
IGNORE=         module name conflict with a different implementation in
base system
.endif

>  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 ?

I would like to continue using sysutils/pam_xdg because it handles all
${XDG_*_HOME}, and local name spaces.

2: https://cgit.freebsd.org/ports/tree/sysutils/pam_xdg/Makefile#n16

Thanks.