Vifm 0.7.4 is out. Some info from homepage: 0.7.4 is a minor release, which improves existing features as well as adds some new ones. Main changes: New multicolumn view. New ls-like view (see 'lsview' option) and related keys for it. Prefixes and suffixes of files of different types are configurable now. Smarter handling of file associations (now vifm will try to find existing program). Some basic means to do scripting (if-else-endif statements, builtin functions, comparison operators). Reduced history memory consumption. Better configure script, which now checks more stuff (and does it in a more accurate way) needed to build vifm.
UPD: Vifm 0.7.4a is out fixing bugs related to new stuff in 0.7.4.
Created attachment 333714 [details] Updated ebuild to emerge vifm 0.7.4a This ebuild enables building version 0.7.4a of vifm. Changes made: 1) removed compatibility use flag as that no longer exists. 2) added X11 useflag. New option used to retrieve terminal titles. 3) add gtk useflag. Used to determine mime titles of files. 4) Packaging of tarbal has changed compared to 0.7.2 and is now extracted as directory, which is incorporated. With this ebuild vifm build successfully. However I am a bit unsure about the dependencies as set for X11 and gtk. Looks OK, but please double-check in particular for the gtk dependency.
Created attachment 333718 [details] ebuild that also install the required help file metioned in elog. Didn't double-check that advise at end of ebuild to install the helpfile using helptags wasn't copied during install. This ebuild corrects this omission.
I suggest changing USE-flag "vim-plugin" to "vim" (to match other packages installing vim plugins) and enabling it by default. vifm users most probably use vim as well, so I don't see why it should be disabled by default.
This ebuild works also for vifm-0.7.4b. Dependencies for gtk seems to be right: configure.in use just glib-2.0 and gtk+-2.0. Why do not disable X and gtk flags by default? Is it not default choice for console programs? (In reply to comment #2) > Created attachment 333714 [details] > Updated ebuild to emerge vifm 0.7.4a > > This ebuild enables building version 0.7.4a of vifm. Changes made: > > 1) removed compatibility use flag as that no longer exists. > 2) added X11 useflag. New option used to retrieve terminal titles. > 3) add gtk useflag. Used to determine mime titles of files. > 4) Packaging of tarbal has changed compared to 0.7.2 and is now extracted as > directory, which is incorporated. > > With this ebuild vifm build successfully. However I am a bit unsure about > the dependencies as set for X11 and gtk. Looks OK, but please double-check > in particular for the gtk dependency.
(In reply to comment #5) > Why do not disable X and gtk flags by default? Is it not default choice for > console programs? These USE-flags aren't enabled by default, so if you haven't enabled them in make.conf, package.use or by selecting desktop profile, they would be disabled. If anyone's interested, I can keep recent vifm ebuilds in rion overlay, until somebody like wired wakes up :)
(In reply to comment #6) > (In reply to comment #5) > > Why do not disable X and gtk flags by default? Is it not default choice for > > console programs? > These USE-flags aren't enabled by default, so if you haven't enabled them in > make.conf, package.use or by selecting desktop profile, they would be > disabled. Sorry, if i am wrong. Do not mean those +'s that X and gtk flags are enabled by default? From ebuild: IUSE="+X +extended-keys +magic +gtk vim-plugin vim-syntax"
(In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Why do not disable X and gtk flags by default? Is it not default choice for > > > console programs? > > These USE-flags aren't enabled by default, so if you haven't enabled them in > > make.conf, package.use or by selecting desktop profile, they would be > > disabled. > Sorry, if i am wrong. Do not mean those +'s that X and gtk flags are enabled > by default? > From ebuild: > IUSE="+X +extended-keys +magic +gtk vim-plugin vim-syntax" Sorry, I have somehow looked into wrong ebuild. You're right, IUSE is a bit wrong and should be changed.
So... 0.7.4b-r1 is now in the tree :) -r0 was a failed experiment using the vim-plugin eclass :P USE="vim" enables the vim plugin and vim-compatible docs now. The ebuild is smart enough to properly install vim-compatible documentation when you have the vim USE enabled, so now you don't have to do any post-install work and should remove any files manually installed in ~/.vim/. Thanks for the bug, your contributions and your patience :)
