Jump to content
Forums in Read-Only Mode - Please use Reddit ×
  • 0

Another stupid ego -- kits -- local overlay question

rsa4046

Asked by rsa4046,

 Share

Question

rsa4046 Newbie

rsa4046

Posted
Posted

I need to maintain some local overlays (mostly tied to various ::science ebuilds), and had done so using the sequence https://www.funtoo.org/Local_Overlay, i.e. 

# mkdir /var/git/overlay
# cd /var/git/overlay
# git clone  http://github.com/funtoo/skeleton-overlay.git
# mv skeleton-overlay myoverlayname
# echo "myoverlayname" > /var/git/overlay/myoverlayname/profiles/repo_name
# echo "masters = core-kit" >> /var/git/overlay/myoverlayname/metadata/layout.conf

# echo "[myoverlayname]" >> /etc/portage/repos.conf/myoverlayname.conf
# echo "location = /var/git/overlay/myoverlayname" >> /etc/portage/repos.conf/myoverlayname.conf
# echo "masters = core-kit" >> /etc/portage/repos.conf/myoverlayname.conf
# echo "auto-sync = no" >> /etc/portage/repos.conf/myoverlayname.conf
# echo "priority = 10" >> /etc/portage/repos.conf/myoverlayname.conf

This has worked fine: I could sync portage with 'ego sync', and still have access to the ebuilds within these overlays. However, running 'ego sync' now nukes these overlays -- note "Removing repos.conf/..." messages below 

# ego sync
Syncing meta-repo
Already on 'master'
Your branch is up-to-date with 'origin/master'.
HEAD is now at 9a39aea kit updates
Removing repos.conf/funtoo
Removing repos.conf/mylocal.conf
Removing repos.conf/science.conf
Already up-to-date.
Syncing core-kit branch 1.0-prime
Already on '1.0-prime'
Your branch is up-to-date with 'origin/1.0-prime'.
HEAD is now at 9e060d4c updates
Already up-to-date.
Syncing core-hw-kit branch master
Already on 'master'
Your branch is up-to-date with 'origin/master'.
HEAD is now at e385111 updates
Already up-to-date.
Syncing security-kit branch 1.0-prime
Already on '1.0-prime'
Your branch is up-to-date with 'origin/1.0-prime'.
HEAD is now at ff9ab7f updates
Already up-to-date.
WARNING: Kit xorg-kit branch master specified in ego.conf is not currently active; using default kit instead.
Syncing xorg-kit branch 1.17-prime
Already on '1.17-prime'
...

So I presume that I should no longer be using 'ego sync' and just sync manually, i.e., 

# cd /var/git/meta-repo/
# git pull
# git submodule update
# cd /var/git/meta-repo/kits/xorg-kit/
# git checkout master
# git pull
# cd
# chown -R portage:portage /var/git/meta-repo
# eix-update

Is that correct or am I missing something?

Link to comment
Share on other sites

5 answers to this question

Recommended Posts

  • 2
  • Funtoo Linux Developer
pytony Newbie

pytony

Posted
  • Funtoo Linux Developer
Posted

It looks like you have your /etc/portage/repos.conf symlinked to /var/git/meta-repo/repos.conf.

try: 

rm /etc/portage/repos.conf
rm /var/git/meta-repo/repos.conf/funtoo
mkdir /etc/portage/repos.conf/
ln -s /var/git/meta-repo/repos.conf /etc/portage/repos.conf/funtoo
for f in /var/git/meta-repo/repos.conf/*.conf; do mv "$f" /etc/portage/repos.conf/; done

 

Link to comment
Share on other sites
  • 0
rsa4046 Newbie

rsa4046

Posted
  • Author
Posted

Hi Oleg, thanks for the quick reply. Here's contents of /etc/portage 

# ls -dl /etc/portage/*/* 
-rw-r--r-- 1 root    root    1472 Nov  3 10:53 /etc/portage/make.profile/parent
-rw-r--r-- 1 root    root     274 Jun 15 18:48 /etc/portage/package.accept_keywords/package.accept_keywords
-rw-r--r-- 1 root    root    1013 Sep  4 13:37 /etc/portage/package.license/package.license
-rw-r--r-- 1 root    root     293 Oct 16 14:25 /etc/portage/package.mask/package.mask
-rw-r--r-- 1 root    root     522 Sep  9 22:40 /etc/portage/package.mask/science
-rw-r--r-- 1 root    root     947 Sep  8 15:04 /etc/portage/package.unmask/package.unmask
-rw-r--r-- 1 root    root    1640 Sep 22 10:00 /etc/portage/package.unmask/test
-rw-r--r-- 1 root    root    5583 Nov  1 13:17 /etc/portage/package.use/package.use
-rw-r--r-- 1 root    root       0 Oct  9 13:21 /etc/portage/package.use/science
drwxr-xr-x 1 root    root      42 Jun  9 10:51 /etc/portage/patches/x11-drivers
drwxr-xr-x 1 root    root       0 Oct 26 17:09 /etc/portage/profile/package.provided
-rw-r--r-- 1 root    root    1656 Oct 16 19:20 /etc/portage/repo.postsync.d/example
-rwxr-xr-x 1 root    root     153 Sep  7 15:35 /etc/portage/repo.postsync.d/q-reinit
-rw-r--r-- 1 portage portage   89 Oct 23 12:45 /etc/portage/repos.conf/core-hw-kit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/core-kit
-rw-r--r-- 1 portage portage   31 Oct 23 12:45 /etc/portage/repos.conf/default
-rw-r--r-- 1 portage portage   89 Oct 23 12:45 /etc/portage/repos.conf/desktop-kit
-rw-r--r-- 1 portage portage   81 Oct 23 12:45 /etc/portage/repos.conf/dev-kit
-rw-r--r-- 1 portage portage   89 Oct 23 12:45 /etc/portage/repos.conf/editors-kit
lrwxrwxrwx 1 portage portage   30 Nov  3 10:54 /etc/portage/repos.conf/funtoo -> /var/git/meta-repo/repos.conf/
-rw-r--r-- 1 portage portage   85 Oct 23 12:45 /etc/portage/repos.conf/games-kit
-rw-r--r-- 1 portage portage   86 Oct 23 12:45 /etc/portage/repos.conf/gnome-kit
-rw-r--r-- 1 portage portage   89 Oct 23 12:45 /etc/portage/repos.conf/haskell-kit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/java-kit
-rw-r--r-- 1 portage portage   81 Oct 23 12:45 /etc/portage/repos.conf/kde-kit
-rw-r--r-- 1 portage portage   83 Oct 29 09:09 /etc/portage/repos.conf/lang-kit
-rw-r--r-- 1 portage portage   97 Oct 23 12:45 /etc/portage/repos.conf/lisp-scheme-kit
-rw-r--r-- 1 portage portage   85 Oct 23 12:45 /etc/portage/repos.conf/media-kit
-rw-r--r-- 1 portage portage   89 Oct 23 12:45 /etc/portage/repos.conf/ml-lang-kit
-rw-r--r-- 1 portage portage   94 Nov  3 10:56 /etc/portage/repos.conf/mylocal.conf
-rw-r--r-- 1 portage portage   81 Oct 23 12:45 /etc/portage/repos.conf/net-kit
-rw-r--r-- 1 portage portage   81 Oct 23 12:45 /etc/portage/repos.conf/nokit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/perl-kit
-rw-r--r-- 1 portage portage   81 Oct 23 12:45 /etc/portage/repos.conf/php-kit
-rw-r--r-- 1 portage portage   87 Oct 23 12:45 /etc/portage/repos.conf/python-kit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/ruby-kit
-rw-r--r-- 1 portage portage   90 Oct 23 12:45 /etc/portage/repos.conf/science-kit
-rw-r--r-- 1 portage portage   94 Nov  3 10:56 /etc/portage/repos.conf/science.conf
-rw-r--r-- 1 portage portage   91 Oct 23 12:45 /etc/portage/repos.conf/security-kit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/text-kit
-rw-r--r-- 1 portage portage   83 Oct 23 12:45 /etc/portage/repos.conf/xfce-kit
-rw-r--r-- 1 portage portage   83 Nov  3 09:54 /etc/portage/repos.conf/xorg-kit
drwxr-xr-x 1 root    root      28 Sep  7 17:31 /etc/portage/savedconfig/sys-apps
#

I notice that there is some mixed user:group ownership between root and portage ... should /etc/portage be entirely portage:portage?

Link to comment
Share on other sites
 Share
Go to question listing
×
×
  • Create New...