Re: sysutils/pam_xdg: Cancelled on -CURRENT

On 2024-03-19 16:02, Emmanuel Vadot wrote:
> On Tue, 19 Mar 2024 07:55:15 +0000
> Alastair Hogge <agh@riseup.net> wrote:
> 
>> 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
> 
>  Ah yes, I've missed this :)
> 
>> >  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.
> 
>  XDG_*_HOME variables aren't needed, all applications must have a
> fallback to the base directories in the spec and sysutils/pam_xdg
> doesn't offer to use other directories so that's why I didn't implement
> those in the base one.
>  What do you mean by "local name spaces" ?

I meant all the other ${XDG_FU} excluding ${XDG_*_HOME}.

Anyways, turns out incredibly mistaken. I deployed another corporate
craptop from the dumpster today, and the User's homedir was not
populated with XDG dirs. I was sure I was using sysutils/pam_xdg for
that, but will now have to find my older scripts that predate using
sysutils/pam_xdg, to achieve that. Sorry for the noise.

Thanks,
Alastair