It would be useful if eix could indicate when a binpkg is available in PKGDIR. I would suggest either an indicator on the "Available versions" line or an extra "Binary versions" line which is only shown on request / when available.
I suppose this can be closed: eix-0.18.2 with support for tbz2 is in the tree.
I've just installed 0.18.2 and am unable to see how it's indicating the availability of binpkg's. I have binpkgs for eix 0.17.0 and 0.18.2 in PKGDIR. # eix eix [I] app-portage/eix Available versions: 0.17.0 ~0.17.1 ~0.18.0 (~)0.18.2 {bzip2 deprecated doc nls sqlite tools} Installed versions: 0.18.2(08:46:25 12/10/09)(bzip2 nls -deprecated -doc -sqlite -tools) Homepage: http://eix.sourceforge.net Description: Search and query ebuilds, portage incl. local settings, ext. overlays, version changes, and more According to the description, the new bzip2 use flag on eix is nothing to do with the feature I described in this request: # quse -D bzip2 global:bzip2: Use the bzlib compression library local:bzip2:app-arch/libarchive: Allow accessing bzip2-compressed archives through libbz2 (which comes with bzip2). local:bzip2:app-portage/eix: Support for parsing of environment.bz2 to guess repository name of packages installed with ancient portage versions (requires app-arch/bbzip2). This flag is safe to disable for portage users that have re-merged all packages since 2007. This flag will be phased out. Am I missing something?
(In reply to comment #2) > I have binpkgs for eix 0.17.0 and 0.18.2 in PKGDIR. Please check: Do the files $PKGDIR/app-portage/eix-0.17.0.tbz2 $PKGDIR/app-portage/eix-0.18.2.tbz2 really exist? If I create them (even if empty), I get the output [I] app-portage/eix Available versions: 0.17.0{tbz2} (~)0.17.1 (~)0.18.0 (~)0.18.2{tbz2} ... But now I recall that ancient portage versions made symlinks instead of ordinary files in the CATEGORY subdirectories - eix does not recognize symlinks as files in this respect (this will be fixed in eix-0.18.3). Can you confirm that you have symlinks and no files there? > the new bzip2 use flag on eix is nothing to do with the feature Indeed, this is unrelated: The bzip2 flag is only important if e.g. you have no file /var/db/pkg/app-portage/eix-0.18.2/repository (which would be the case if you installed it with an ancient portage version); In this case eix can attempt to parse the file /var/db/pkg/app-portage/eix-0.18.2/environment.bz2 to get the same information from a stored environment variable. This feature was automatically activated in earlier eix ebuilds; now it is optional, since most users will not need it.
# emerge --version Portage 2.2_rc45 (default/linux/x86/10.0, gcc-4.3.2, glibc-2.9_p20081201-r2, 2.6.18-xen-r12 x86_64) # eix --version eix 0.18.2 (gcc-4.3.2, i686-pc-linux-gnu) # emerge --info | grep PKGDIR PKGDIR="/usr/portage/packages" ls -l /usr/portage/packages/app-portage/eix-* lrwxrwxrwx 1 root root 22 2009-04-23 03:02 /usr/portage/packages/app-portage/eix-0.15.7.tbz2 -> ../All/eix-0.15.7.tbz2 lrwxrwxrwx 1 root root 22 2009-05-25 14:30 /usr/portage/packages/app-portage/eix-0.16.0.tbz2 -> ../All/eix-0.16.0.tbz2 lrwxrwxrwx 1 root root 22 2009-06-12 19:57 /usr/portage/packages/app-portage/eix-0.16.1.tbz2 -> ../All/eix-0.16.1.tbz2 lrwxrwxrwx 1 root root 22 2009-06-29 09:48 /usr/portage/packages/app-portage/eix-0.16.2.tbz2 -> ../All/eix-0.16.2.tbz2 lrwxrwxrwx 1 root root 22 2009-07-07 18:26 /usr/portage/packages/app-portage/eix-0.17.0.tbz2 -> ../All/eix-0.17.0.tbz2 lrwxrwxrwx 1 root root 22 2009-10-12 08:46 /usr/portage/packages/app-portage/eix-0.18.2.tbz2 -> ../All/eix-0.18.2.tbz2 They are symlinks, but hardly an ancient portage version!
Adjusting severity of the bug then... In portage-2.2 this has been fixed very long - I am surprised that it wasn't fixed in the stable portage yet, since one can just wait for collisions with virtual packages of the same name and version... Anyway, you will have to wait until eix-0.18.3 for the fix concerning eix.
Just run the "move-from-all" script on Bug #133908 and the tbz2 flag shows up as intended now. At a guess, what happens is that until the "All/" directory is removed from PKGDIR, portage continues to use the old style behavior. I never noticed this as I tend to just leave things alone if they're working how I want them to =)
(In reply to comment #5) > Anyway, you will have to wait until eix-0.18.3 for the fix concerning eix. > in portage tree.
