Re: A fix for pkgtools/mksandbox

[Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>]

On 17/12/2025 14:45, Taylor R Campbell wrote:

> Instead, can we pass configure arguments or something to security/sudo
> so that it does the right thing?

Probably not for two reasons. 1) If we knew what the "right" system 
directory was for configuring security/sudo, we could just put that 
knowledge into mksandbox. 2) security/sudo will probably refuse to 
configure if the directory doesn't exist.

> Alternatively, does the sudo build look for different directories on
> specific operating systems?  Having something like
>
> 	case $opsys in
> 	SunOS)
> 		mkdir $sandbox/var/adm
> 		;;
> 	Linux)
> 		mkdir $sandbox/var/lib
> 		;;
> 	...
> 	esac
>
> wouldn't be so bad (adjust according to what is appropriate for the
> operating systems).

That was my first idea and I rejected it because I didn't know what 
operating systems mksandbox runs on. I now know what operating systems 
mksandbox runs on because it has a case statement just like that in it.

I don't know what all the right directories are, but I am perfectly 
willing to add the ones that I do know and put in comments for the 
others to the case statement. That will fix NetBSD, Linux and macOS[*] 
while leaving the others no worse off than they are right now.

If that's OK, I'll try and mail through an alternative patch today.

Ngā mihi,
Lloyd

[*] Darwin is disabled in pkgsrc, but it's still in the mksandbox script 
and I know what the right directory is, so I should put it in.