From: William McGonagle <wmcgonagle443@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Proper overlay permissions
Date: Thu, 31 Oct 2024 15:58:52 -0700 [thread overview]
Message-ID: <CAGjDVnmpoJSAORQ1C4bgD1Yw2HeEuebD1Ydy+6Go4V_UdNgNaA@mail.gmail.com> (raw)
In-Reply-To: <bc80211e-be80-4be1-c5a2-2183a4e106b9@gmail.com>
I got it working! i had to add my repo directory to the safe.directory
variable in my global git config. I also made myself the owner, and
made the group portage. I hope your greens grow beautifully!
On Thu, Oct 31, 2024 at 1:13 PM Dale <rdalek1967@gmail.com> wrote:
>
> I just added a overlay, regular one, plus I have one of my own. I added
> one right after my initial install, voyager. Keep in mind, I run emerge
> and such as root. It won't matter for me but if you plan to run emerge
> as a user, it will matter. This is what mine looks like.
>
>
> root@Gentoo-1 / # ls /var/db/repos/
> total 24
> drwxr-xr-x 6 root root 4096 Oct 30 12:29 .
> drwxr-xr-x 7 root root 4096 Oct 30 12:38 ..
> drwxr-xr-x 177 portage portage 4096 Oct 26 01:11 gentoo
> drwxr-xr-x 144 root root 4096 Oct 30 12:29 guru
> drwxr-xr-x 4 root root 4096 Oct 30 12:37 localrepo
> drwxr-xr-x 23 root root 4096 Oct 30 12:35 voyageur
> root@Gentoo-1 / #
>
>
> As you can see, the gentoo directory is portage:portage. However, my
> local overlay and two regular overlays are root:root. That is likely
> because I was root when I added them. The benefit of portage:portage is
> that you can add a user to the portage group and it should work
> permissions wise. If I added my user to the portage group and tried to
> run emerge, I'd likely get a permissions error with the settings above.
>
> Like I said, I'm no guru but if I'm wrong, odds are someone will chime
> in soon. Of course, you could just try it and see if it works. If not,
> change it back. ;-)
>
> Dale
>
> :-) :-)
>
> P. S. My garden is about to get rain. It's been at least a month since
> last one. My greens will be so happy. :-D
>
>
> William McGonagle wrote:
> > I appreciate the advice, I will try that. I just installed a few days
> > ago, and all my overlays are owned by root. I've seen a lot of
> > conflicting info on this, but I don't see how changing the permissions
> > like you said could cause any problems. Thanks again!
> >
> > On Thu, Oct 31, 2024 at 7:40 AM Dale <rdalek1967@gmail.com> wrote:
> >> William McGonagle wrote:
> >>> I want to develop a local overlay on my system, sync it with git, and
> >>> be able to sign my commits with gpg. How can i set the permissions of
> >>> my overlay so that I can do this as a regular user securely? Would it
> >>> be fine to just make me the owner of that directory?
> >>>
> >>>
> >>
> >> I'm no expert at this but in the past, I set permissions this way.
> >> portage:portage and then add the user to the portage group. When you
> >> first install Gentoo, that is the default permissions, last I looked
> >> anyway. That should work.
> >>
> >> Hope that helps.
> >>
> >> Dale
> >>
> >> :-) :-)
> >>
> >
>
>
prev parent reply other threads:[~2024-10-31 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 3:42 [gentoo-user] Proper overlay permissions William McGonagle
2024-10-31 14:39 ` Dale
2024-10-31 19:17 ` William McGonagle
2024-10-31 20:12 ` Dale
2024-10-31 22:58 ` William McGonagle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGjDVnmpoJSAORQ1C4bgD1Yw2HeEuebD1Ydy+6Go4V_UdNgNaA@mail.gmail.com \
--to=wmcgonagle443@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox