Search the Community
Showing results for tags 'eselect'.
Found 3 results
Good morning after a bit of a rocky transition to the new kit setup, I've noticed that eselect set python X doesn't seem to be working: mediaserver ~ # eselect python list Available Python interpreters, in order of preference:  python3.4  python3.6  python2.7 (fallback) mediaserver ~ # eselect python set 1 mediaserver ~ # eselect python list Available Python interpreters, in order of preference:  python3.4  python3.6  python2.7 (fallback) No asterisk after python3.4 However eselect kernel seems to be working appropriately: mediaserver ~ # eselect kernel list Available kernel symlink targets:  linux-4.9.4-gentoo  linux-4.9.7-gentoo  linux-4.10.1-gentoo  linux-4.10.4-gentoo  linux-4.10.13-gentoo  linux-4.11.3-gentoo  linux-4.12.1-gentoo  linux-4.12.4-gentoo  linux-4.13.3-gentoo *  linux-4.13.4-gentoo  linux-4.13.5-gentoo Is this normal? THanks in advance,
Putting my sever setup together (move from debian -> funtoo) I faced the issue of installing php5. I found enough docs to walk me through issues/pitfalls to get going. However, when I emerged dev-libs/php5 I got something unexpected back. emerge complained about the dependencies built into the app-admin/eselect-php ebuild (ver 0.7.1-r3). It seems that the version of php available was "too new". The available php version was 5.5.19 but eselect-php had a hard dependency of "!<dev-lang/php-5.5.0_beta1-r2". Well, that seems silly. So I followed the steps for making a Local Overlay , copied the ebuild, updated the slot numbers to the latest available for php 5.3,5.4 and 5.5. I also added the files referenced by the ebuild. I did the emerge of php and got everything working. Yulp!!!! Touchdown!!! :D This whole process of making local overlays to correct 'perceived' upstream oversights is disconcerting. It seems to me rather deceptively easy to just overwrite version dependencies. Please tell me there's more too this. During the search for a workaround to the eselect-php ebuild, I stumbled on the exact same issue ( FL-469 ) from March 2013. This gives me the impression that hard coding the version dependencies into ebuilds creates a "whack-a-mole" situation where updating dependency info in ebuilds is a constant necessity. What's the best way to fix/update/help?
The www-client/firefox 'plugin check' indicates that my Java Plugin 10.67.2 is vulnerable. Currently I have dev-java/oracle-jdk-bin:1.7 (188.8.131.52) installed and eselect java-nsplugin is therefore set to oracle-jdk-bin-1.7. Looking at available packages I see that there is a 1.8 version (184.108.40.206). So I went ahead and installed this version with emerge --oneshot oracle-jdk-bin:1.8 eselect java-nsplugin now lists 1.7 and 1.8 however if I attempt to set 1.8 it fails with the following message !!! Error: Usage: set [32bit or 64bit] [nsplugin-vm] exiting It is also worth noting that I receive a similar message if trying to set version 1.8 for eselect java-vm !!! Error: Usage [user|system] [vm] exiting What am I doing wrong? :wacko: