/usr/pkgsrc ownership

pfr

I'm not sure if I did something wrong when I installed, but when running anything inside /usr/pkgsrc i'm asked for su permission. Is this usual behavior?
for example, when running git pull -r /usr/pkgsrc/wip I get permission denied. I cant even run make to build packages without getting permission denied.

It look like /usr/pkgsrc belongs to 600 while everything else in /usr is owned by root I don't remember doing anything differently this time around, but I never had to run these with doas in the past.

I've looked in the pkgsrc guide but couldn't find anything about permissions

Jay

pfr hi you need to give /usr/pkgsrc/wip folder user permissions.
chown user ../wip

pfr

Jay Thanks Jay. I still get permission denied after I doas chown user /usr/pkgsrc/wip

EDIT: It worked using doas chown -R user /usr/pkgsrc/wip

However, what about my entire /usr/pkgsrc folder? should I chown it aswell?

Jay

pfr you don't need to chown whole pkgsrc you can use doas/sudo

Jay

Also check this https://www.netbsd.org/docs/pkgsrc/faq.html#using-sudo-with-pkgsrc

pfr

I don't want sudo on my system, I'm happy using doas. However, as I understand it I should use make to build a package as an unprivileged user, then only invoke doas when installing with make install but I'm not able to build without becoming a privileged user.

Jay

pfr you might be able to use doas as replacement to sudo as shown in above link.

@Jay doas's persist option is only available on native OpenBSD.
You can usedoas instead of sudo but, as the persist option is missing, you have to actually type your password at every invocation of the command.

@pfr I've told you in a PM how I handle this myself. I won't quote it here, as its not the recommended way.
Have a look at section 10.3 of the guide and at
unprivileged.mk.

nia

Honestly... keeping pkgsrc in /usr/pkgsrc is bad advice. Don't build things as root, either.

I keep it in my home directory. Don't bootstrap unprivileged, a default NetBSD install has everything needed to install packages system-wide. If you set SU_CMD to sudo as described in the pkgsrc guide, you can build everything as your local user and it will escalate appropriately to install things providing you have configured sudo to allow the escalation without a password (see wheel group stuff in the default config file)...

If you are dead against adding yourself to the wheel group and allowing escalation without a password, you can create a pkgdev user or something. To me the purpose of requiring commands to be prefixed with sudo is to prevent mistakes, it's not security.

pfr

nia So it's safe to move the entire pkgsrc directory to /home/$USER/pkgsrc/ ? And if I was to do that, what files do I need to edit.

nia

pfr Don't need to edit any files. Honestly, delete /usr/pkgsrc, download a fresh pkgsrc tarball:

https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc.tar.xz

https://cdn.netbsd.org/pub/pkgsrc/pkgsrc-2020Q2/pkgsrc.tar.xz

extract it in /home -xzcat pkgsrc.tar.xz | tar xvf -, then cd pkgsrc && cvs -q up -Pd