
You are not logged in.
Pages: 1
Here's an updated how-to on how manage ebuilds locally in your own overlay
Create the necessary directory structure
=======================================
# mkdir -p /usr/local/portage/profiles
# echo "$HOSTNAME" >> /usr/local/portage/profiles/repo_name
This enables access to /usr/local/portage
for users in the portage group
========================================
# chown root:portage /usr/local/portage
Assign the portage group as default for newly created files in
/usr/local/portage
==============================================
# chmod g+s /usr/local/portage
Enable users in the portage group to write to
/usr/local/portage
=============================================
# chmod 775 /usr/local/portageEdit make.conf
==============
# nano -w /etc/make.conf
-Add
PORTDIR_OVERLAY=/usr/local/portage
Logout as root
===============
# exit
Create the relevant directory structure
(I use the game rain-slick as example)
======================================
$ mkdir -p /usr/local/portage/games-rpg/rain-slick
Copy the ebuild to your overlay
===============================
$ cp rain-slick-1.5.ebuild /usr/local/portage/games-rpg/rain-slick
Issue the following commands to install rain-slick from your overlay
====================================================================
$ cd /usr/local/portage/games-rpg/rain-slick
$ ebuild rain-slick-1.5.ebuild digest
$ su
# emerge -a rain-slickLast edited by Kasumi_Ninja (2010-10-14 20:36:11)
Offline
I there! Only a little suggestion for readability : it would be nice to add something like "# " in front of commands, to help distinguish between comments and actual commands ![]()
Oh, and a typo : emerge-a -> emerge -a
Offline
I there! Only a little suggestion for readability : it would be nice to add something like "# " in front of commands, to help distinguish between comments and actual commands
Oh, and a typo : emerge-a -> emerge -a
Thanks for the suggestion!
Offline
Nice how-to ![]()
I do have a suggestion though.
Don't you think allowing anyone other than root to have write access to the manifests poses a significant security risk? Anything could be slipped into an ebuild file and since that same user can also create the manifests, you can't even rely on them to protect you from tampering. I would at least recommend creating the manifests as root or otherwise making them read only for everyone but root. That would give you some protection against tampering while still making it convenient to add and remove things from your overlay. Although personally, I only allow root write access to my entire overlay.
Offline
I never heard of using "ebuild NAME_Of_EBUILD digest" before. I was always taught to use "ebuild NAME_Of_EBUILD manifest". Any difference between the two or do they basically do the same thing?
Offline
according to "man ebuild" digest and manifest do both recreate the manifest/checksums.
Although only digest was available in earlier version, it became deprecated in favor of manifest.
I guess digest is being kept for compatibility reasons...
Offline
FYI. If you have your own local overlay and have several machines running funtoo(gentoo), you can register github and use git to manager your overlay. With this, you can easily share local overlay among your machines and share it with other funtoo/gentoo users.
>>>Gentoolizing, say goodbye to ubuntu.
My personal overlay https://github.com/cchalpha
Offline
Added to wiki page ( http://www.funtoo.org/wiki/Git_local_overlay ), correct me if there is some mistakes.
Coffee, which sticks to the spoon and dries up there is the most delicious thing in the world.
Offline
Pages: 1