Talk:Creating an ebuild repository
Before creating a discussion or leaving a comment, please read about using talk pages. To create a new discussion, click here. Comments on an existing discussion should be signed using
~~~~:
A comment [[User:Larry|Larry]] 13:52, 13 May 2024 (UTC) : A reply [[User:Sally|Sally]] 15:12, 30 December 2024 (UTC) :: Your reply ~~~~
Crossdev priority
Setting the priority of the crossdev overlay to 9999 caused crossdev to choose the wrong overlay. If I set it to the lowest priority, e.g., 1, it works. Can others confirm this?
- I had also some problems with crossdev and setting the right overlay. For me it was solved with setting crossdev and not local-crossdev in /usr/local/portage-crossdev/profiles/repo_name and in /etc/portage/repos.conf/crossdev.conf
- from # crossdev --help
-oO, --ov-output path Overlay to write crossdev package links
[default: uses repo with name 'crossdev', or
'cross-${CTARGET}', or falls back to first
from --overlays list]
/usr/local/portage-crossdev/metadata/layout.confmasters = gentoo
thin-manifests = true
/etc/portage/repos.conf/crossdev.conf[crossdev]
location = /usr/local/portage-crossdev
priority = 10
masters = gentoo
/usr/local/portage-crossdev/profiles/repo_namecrossdev
--Vitalogy (talk) 16:32, 31 January 2016 (UTC)
This doesn't seem to be accurate. crossdev only ever selects the lowest priority and lexicographically last overlay, no matter what name it has (or whether there is an existing overlay named "cross-${CTARGET}" or "${CTARGET}". This is a pain when working with multiple crossdev overlays and having to remember to manually specify the overlay every time.
--Petteyg (talk) 17:20, 15 October 2016 (UTC)
Merge with "Overlay"
How about merging this with the original "Overlay" page, because there needs to be replaced some outdated information for which here the newer one is. I thought adding a paragraph in "Overlay" about local overlays. Columbus (talk) 13:11, 6 May 2015 (UTC)
- TL;DR: Please update/fix things, but don't move steps out of step-by-step instructions :-)
- There is a section "1.5 Local overlay" in Overlay containing a link to Overlay/Local_overlay, the link can be replaced with the full text if header levels are adjusted.
- Fwiw, the original reasoning for using a separate page was that the Overlay page covered too many topics in too great detail, resulting in a page unsuited for use as a step-by-step guide. IMO it should be possible for a new user to follow instructions for common tasks (like installing a 3rd party ebuild) without first reading a long introduction on gentoo's overlay system and portage's various configuration files or hunting down information that is spread around in different sections of a page. This is also the approach taken in the Handbook.
- Judging by the banner at the top of the Overlay page it is currently outdated, which is extra bad for pages that are immediately useful for new users. I would prefer to be able to point users at a maintainable, self-contained guide rather than a long page that also contains outdated, incorrect or potentially harmful information. Eroen (talk) 07:39, 7 May 2015 (UTC)
- Instead of merging into Overlay please think of transcluding it there. Then, maintenance could be done in [Custom_ebuild_repository|[Overlay/Local_overlay]] and the full content were visible in Overlay. --Charles17 (talk) 08:32, 7 May 2015 (UTC)
Article rename: Custom repository -> Custom ebuild repository
I propose this article be named "Custom ebuild repository" instead of "Custom repository". "Custom repository" is too generic. There are all kinds of repositories for various projects, but this article is referring specifically to repositories containing ebuilds (and their associated data). If I see no replies in 30 days I'll move this article. Kind regards, --Maffblaster (talk) 23:55, 24 May 2017 (UTC)
- But please keep in sync with section header of the handbook article.--Charles17 (talk) 11:42, 25 May 2017 (UTC)
Only a few year later, but now this is done. I guess that's what we get for not having a great way to track open discussion / todo items. --Maffblaster (talk) 22:53, 26 October 2020 (UTC)
Creating Manifest and digest
To create a Manifest and digest for an ebuildː
user $pwd/usr/local/portage/bar
root #ebuild foo.ebuild digest>>> Creating Manifest for /usr/local/portage/bar/foo
where foo.ebuild is the ebuild bar/foo --Jms (talk) 00:52, 11 March 2019 (UTC)
- Yes, this is an alternative way to do this. The article already describes using repoman manifest to accomplish this same task. Do we really need to spell out both ways? --Grknight (talk) 13:43, 11 March 2019 (UTC)
This way we don't need to install repoman . Less is more. --Jms (talk) 14:18, 11 March 2019 (UTC)
- You probably still want repoman installed if you are doing any developer work at all. Repoman provides debug output when writing ebuilds. =) --Maffblaster (talk) 03:55, 12 March 2019 (UTC)
eselect approach also for crossdev
Regarding the work-in-progress note from User:Ris does initiating with eselect repository create yield what is described under Crossdev#Crossdev overlay? If so Crossdev should instead read:
root #eselect repository create crossdevAlso linking here?
--Onkobu (talk) 19:05, 27 December 2021 (UTC)
- I think it should work, yes. That could probably be replaced in the crossdev article with the simpler version, yes - I suspect that those instructions were written before eselect repository existed.
- I'll close this conversation in a few days, if there is nothing to add, to keep open conversations down. Happy holidays ^^. -- Ris (talk) 19:16, 27 December 2021 (UTC)
Outstanding Todo items
Moved from the main article; tidy up as these are actioned
Todo:
- Section on methods to share an ebuild repository (github, rsync...) / how to provide synchronization for an ebuild repository that has been shared.
- Section on how to register an ebuild repository on r.g.o.
Kangie (talk) 07:18, 30 October 2023 (UTC)
Installing pkgdev, pkgcheck
It would be helpful to get the hint that pkgdev and pkgcheck are in two separate packages and have to be emerge'd.