| View previous topic :: View next topic |
| Author |
Message |
thomai
n00b
Joined: 05 Jan 2015
Posts: 10
|
 Posted: Sun Mar 22, 2015 7:36 pm Post subject: Layman ebuilds are ignored |
 |
|
I wanted to install a newer version of monodevelop (portage includes a very old 3.0.2).
So I added the dotnet overlay:
I have the correct ebuilds in the local filesystem:
| Code: |
chef@gentoo ~ $ ls /var/lib/layman/dotnet/dev-util/monodevelop/
files metadata.xml monodevelop-5.0.1.ebuild monodevelop-5.7.0-r1.ebuild
Manifest monodevelop-4.2.3.ebuild monodevelop-5.7.0.ebuild monodevelop-9999.ebuild
|
But portage ignores the ebuilds. What is wrong?
| Code: |
chef@gentoo ~ $ equery y monodevelop
Keywords for dev-util/monodevelop:
| | u |
| a a a p s | n |
| l m r h i m m p s p | u s | r
| p d a m p a 6 i p c 3 a x | s l | e
| h 6 r 6 p 6 8 p p 6 9 s r 8 | e o | p
| a 4 m 4 a 4 k s c 4 0 h c 6 | d t | o
---------+-----------------------------+-----+-------
3.0.2-r1 | o + o o o o o o o o o o o + | o 0 | gentoo
|
I added the line in the make.conf
| Code: |
# LAYMAN
source /var/lib/layman/make.conf
|
whichs content is:
| Code: |
PORTDIR_OVERLAY="
/var/lib/layman/dotnet
$PORTDIR_OVERLAY
"
|
$PORTDIR_OVERLAY points correctly to "/var/lib/layman/dotnet" |
|
| Back to top |
|
 |
Budoka
l33t
Joined: 03 Jun 2012
Posts: 777
Location: Tokyo, Japan
|
| Posted: Mon Mar 23, 2015 2:02 am Post subject: |
|
|
| Quote: | I added the line in the make.conf
Code:
# LAYMAN
source /var/lib/layman/make.conf |
I think that this has been deprecated. I was advised to do this in another thread but having said that...I am having the same problem as you.
| Quote: | rather than 'source /var/lib/layman/make.conf' (as you do) they can also be defined in repos.conf, eg:
/etc/portage/repo.conf/foo.overlay.conf
| Code: | [foo-overlay]
location = /var/pkg/foo-overlay |
|
|
|
| Back to top |
|
|
thomai
n00b
Joined: 05 Jan 2015
Posts: 10
|
| Posted: Mon Mar 23, 2015 6:25 am Post subject: |
|
|
Thanks for the tip.
I upgraded portage and layman (to 2.2.18 and 2.3.0) and at first, the ebuilds weren't showing up in "equery y"
Anyway, I could somehow install them by ignoring the search index: "emerge --search-index n -va monodevelop"... |
|
| Back to top |
|
|
dol-sen
Retired Dev
Joined: 30 Jun 2002
Posts: 2805
Location: Richmond, BC, Canada
|
| Posted: Mon Mar 23, 2015 8:18 am Post subject: |
|
|
Two things...
To keep your search index up to date automatically...
| /etc/portage/repo.postsync.d/search-index: | #!/bin/sh
# Example /etc/portage/repo.postsync.d script. Make it executable (chmod +x) for
# Portage to process it.
#
# With portage-2.2.16 and newer, all repo.postsync.d hooks will be called multiple
# times after syncing each repository.
#
# Older versions of Portage support syncing only one repository.
# In those versions, the postsync.d hooks will be called only once,
# and they will not be passed any parameters.
# On a repo.postsync.d hook call, positional parameters contain
# information about the just-synced repository.
# Your hook can control it's actions depending on any of the three
# parameters passed in to it.
#
# They are as follows:
#
# The repository name.
repository_name=${1}
# The URI to which the repository was synced.
sync_uri=${2}
# The path to the repository.
repository_path=${3}
# Portage assumes that a hook succeeded if it exits with 0 code. If no
# explicit exit is done, the exit code is the exit code of last spawned
# command. Since our script is a bit more complex, we want to control
# the exit code explicitly.
ret=0
echo "Re-generating search index for repo: ${repository_name}"
egencache --update-pkg-desc-index --repo "${repository_name}" || ret=1
# Return explicit status.
exit "${ret}"
|
And for layman-2.3.0, migrate to the repos.conf type configuration. Follow the instructions at the portage sync migration page
_________________
Brian
Porthole, the Portage GUI frontend irc@freenode: #gentoo-guis, #porthole, Blog
layman, gentoolkit, CoreBuilder, esearch... |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
