Local portage overlay

[gksudo]

Hi, I set up a local portage repo' on my system and would like some clarification as to whether this is the correct way to do so

Created the ebuild dir

Code: Select all

mkdir -p /usr/local/portage/net-im/discord-canary-bin

Wrote the ebuild to /usr/local/portage/net-im/discord-canary-bin/discord-canary-bin-(version).ebuild

Digest to generate manifest

Code: Select all

ebuild /usr/local/portage/net-im/discord-canary-bin/discord-canary-bin-(version).ebuild digest

Add repo to portage

Code: Select all

/etc/portage/repos.conf/gentoo.conf

[localrepo]
location = /usr/local/portage
auto-sync = no

I found a Wiki article from 2019 (https://linuxreviews.org/HOWTO_make_you ... too_ebuild)
That suggested adding PORTDIR_OVERLAY to make.conf, though the Gentoo Wiki states this is depreciated but still supported?

Thanks, gk

[CaptainBlood]

gksudo,
Welcome to Gentoo.

That suggested adding PORTDIR_OVERLAY to make.conf, though the Gentoo Wiki states this is depreciated but still supported

make.conf PORTDIR_OVERLAY is commented here.
Moreover here's

Code: Select all

cat /etc/portage/repos.conf/local-repo.conf 
[local-repo]
priority=10000
location=/var/db/repos/local-repo

Thks 4 ur attention, interest & support.

[Ionen]

You can use any location for your overlays, but (as used above) /var/db/repos/<name> is probably more standard than /usr/local/portage. If you were still using /usr/portage you may want to migrate to the new (default) /var/db/repos/gentoo location too (and /var/cache/distfiles + /var/cache/binpkgs), but entirely optional.

ebuild location is fine, updating manifest that way is fine too (but "ebuild .. digest" is a synonym for "ebuild .. manifest" now). If you want to go all out you could also use repoman manifest can update the entire overlay at once and perform QA checks, not that QA matters much for a private overlay but I do it anyway for good measure, I use it before submitting ebuild patches to gentoo maintainers too.

repos.conf is what replaces the need for PORTDIR and PORTDIR_OVERLAY, it just gets all the locations from there now (::gentoo included). I still like PORTDIR_OVERLAY for quick testing purposes though, but otherwise both should be removed from make.conf to avoid confusing portage (mismatching PORTDIR between make.conf and repos.conf been known to do strange things, fine if unset).

[gksudo]

Thanks for your responses, after a quick check the gentoo repo is over at /var/db/repos/gentoo. I've cp'd the contents of /usr/local/portage over to /var/db/repos/localrepo
And set the repo config in /etc/portage/repos.conf/localrepo.conf, removed PORTDIR_OVERLAY from make.conf and deleted /usr/local/portage.

Because as of now I only have 1 ebuild to locally maintain, when I update it, ebuild .. manifest seems suitable for now. I'll look into repoman if I start adding my ebuilds

[Hu]

One other use for repoman is that the QA checks, while required for submission to the public repository and optional for your private repository, may flag mistakes that you would choose to fix if you knew they existed. Using repoman would discover these for you, and fixing them there may be less trouble than debugging a problem that ultimately traces back to a QA check. (That said, you don't need to fix every QA issue if you have a good reason for why something doesn't matter to your use case. Use the tool to save you work, not to cause you extra work.)

[charles17]

I found a Wiki article from 2019 (https://linuxreviews.org/HOWTO_make_you ... too_ebuild)

No need for such external references https://wiki.gentoo.org/wiki/Handbook:A ... repository

[gengreen]

One other use for repoman is that the QA checks, while required for submission to the public repository and optional for your private repository, may flag mistakes that you would choose to fix if you knew they existed. Using repoman would discover these for you, and fixing them there may be less trouble than debugging a problem that ultimately traces back to a QA check. (That said, you don't need to fix every QA issue if you have a good reason for why something doesn't matter to your use case. Use the tool to save you work, not to cause you extra work.)

Repoman is great

However I encounter an issue : with repoman 2 I was able to commit msg with the "interactive editor style" (https://github.com/gentoo/musl/pull/193 see the commit msg),

But since repoman 3, this doesn't work anymore... The feature was removed ?