Hi guys,
Eix is one of those packages where you just set it and forget it, and
apparently I've forgotten there was even anything to set.

I have a home PC running gentoo. If I do eix foo, and foo happens to
be keyworded unmasked in my package.keywords, I get for instance:
[I] dev-python/snakeoil
     Available versions:  <yellow>(~)0.3.6.4 (~)0.3.6.5
<block-yellow>(~)0.3.7</block-yellow></yellow>
     Installed versions:  0.3.7(07:34:54  PHT Saturday, 10 July, 2010)
     Homepage:            http://www.pkgcore.org/
     Description:         Miscellaneous python utility code.

I try the same on a relatively young gentoo server I'm managing and
* dev-python/snakeoil
     Available versions:  <yellow>~0.3.6.4 ~0.3.6.5 ~0.3.7</yellow>
     Homepage:            http://www.pkgcore.org/
     Description:         Miscellaneous python utility code.

It's unkeyworded, however, in my package.keywords in both machines:
(home machine)
madum...@trixie ~ $ grep snakeoil -r /etc/portage/package.keywords/
/etc/portage/package.keywords/autounmask-pkgcore:dev-python/snakeoil ~amd64

(server)
mas...@zen ~ $ sudo grep -r snakeoil /etc/portage/package.keywords/
/etc/portage/package.keywords/system.keywords:dev-python/snakeoil ~x86

Apparently I'm missing some environment variable, but I can't for the
life of me imagine how I've set it.
<home PC>
madum...@trixie ~/store/HeCares/Photo upload functionality $ cat /etc/eixrc
# /etc/eixrc
#
# In this file system-wide defaults for variables related to eix binaries
# are stored, i.e. the variables set in this file override the built-in
# defaults. Both can be overridden by ~/.eixrc and by environment variables.
#
# It is strongly recommended to set here only those variables which you
# want to *differ* from the built-in defaults (or for which you have a
# particular reason why the default should never change with an eix update).
#
# *Otherwise you might miss changes in the defaults in newer eix versions*
# which may result in confusing behavior of the eix binaries.
#
# ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in
# /etc/eixrc which is not recommended anymore. If you want to get such a file
# (i.e. a file where all variables are described and set to the current
# values resp. to the built-in default values) you can redirect the output
# of the options --dump or --dump-defaults, respectively.
#
# However once more: To avoid unexpected problems
#
#   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
#
# Only set those for which you have a reason to do so!
#
# For the available variables and their defaults, see the output of the
# options --dump or --dump-defaults.
# For more detailed explanations see the manpage of eix.

madum...@trixie ~/store/HeCares/Photo upload functionality $ cat
/etc/eix-sync.conf
# eix-sync.conf
##  defines options to eix-sync, caching system for portage


#layman overlays to be synced (* means all)
*
</home PC>

<server>
mas...@zen ~ $ cat /etc/eixrc
# /etc/eixrc
#
# In this file system-wide defaults for variables related to eix binaries
# are stored, i.e. the variables set in this file override the built-in
# defaults. Both can be overridden by ~/.eixrc and by environment variables.
#
# It is strongly recommended to set here only those variables which you
# want to *differ* from the built-in defaults (or for which you have a
# particular reason why the default should never change with an eix update).
#
# *Otherwise you might miss changes in the defaults in newer eix versions*
# which may result in confusing behavior of the eix binaries.
#
# ebuilds of <=eix-0.10.3 (and >=eix-0.7.4) used to set *all* variables in
# /etc/eixrc which is not recommended anymore. If you want to get such a file
# (i.e. a file where all variables are described and set to the current
# values resp. to the built-in default values) you can redirect the output
# of the options --dump or --dump-defaults, respectively.
#
# However once more: To avoid unexpected problems
#
#   *IT IS NOT RECOMMENDED TO SET _ALL_ VARIABLES* in /etc/eixrc
#
# Only set those for which you have a reason to do so!
#
# For the available variables and their defaults, see the output of the
# options --dump or --dump-defaults.
# For more detailed explanations see the manpage of eix.

mas...@zen ~ $ cat /etc/eix-sync.conf
cat: /etc/eix-sync.conf: No such file or directory
</server>

All comments for the both of them, so it must be a default I'm missing
that's different for the 2 machines. Any ideas?
-- 
This email is:    [ ] actionable   [ ] fyi        [x] social
Response needed:  [ ] yes          [x] up to you  [ ] no
Time-sensitive:   [ ] immediate    [ ] soon       [ ] none

Reply via email to