Just a quick heads up that if you upgrade xvim in -current, you will need to have the packages acl and attr from slackware/ap installed as well before vim will start. (Xvim actually upgrades to vim 6.4.010 with X support.)

I just did a upgrade using slapt-get and when I tried to use vim to change my fluxbox menu, vim wouldn't start until I had installed acl and attr. Vim had been working fine before and I didn't have acl or attr installed, so I assume that the requirement for libacl and libattr was added in in the recent compile.

Yep, I just had the same experience.

anyone is who using -current
should be reading the changelog
for such information

???

kodon, anyone who tells others that they should read the ChangeLog first should read the ChangeLog first to see if his criticism is valid. There is nothing in the ChangeLog about the requirement for the two libraries.

Here is the line in the ChangeLog that refers to the xvim update:

"xap/xvim-6.4.010-i486-1.tgz: Upgraded to VIM 6.4.010 (with X support.)"

No mention of libacl or libattr.

Okay, here's what happened. Pat split acl, attr, dmapi and xfsdump out into separate packages back on 28.02, so if like me, you didn't catch it then and install the "new" packages, you wouldn't have them. Here is a slice of the ChangeLog from 28.02.2006:

"a/xfsprogs-2.7.11-i486-1.tgz: Upgraded to xfsprogs-2.7.11.
Split acl, attr, dmapi, and xfsdump into separate packages and
moved them into the AP series. This location was a bit of a judgement
call since acl, attr, and dmapi contain libraries, but so do some other
packages outside L. Anyway, it does seem to me that xfsdump should go
in AP, and that these packages should all be found in the same place.
ap/acl-2.2.34-i486-1.tgz: Upgraded to acl-2.2.34, split out of xfsprogs
package.
ap/attr-2.4.28-i486-1.tgz: Upgraded to attr-2.4.28, split out of xfsprogs
package.
ap/dmapi-2.2.3-i486-1.tgz: Upgraded to dmapi-2.2.3, split out of xfsprogs
package.
ap/xfsdump-2.2.33-i486-1.tgz: Upgraded to xfsdump-2.2.33, split out of
xfsprogs package."

So, kadon's criticism might not be so misplaced after all. The lesson here is that when you read through the ChangeLog, you need to consider the effects some of the changes might have on your system and install "new" packages as appropriate.

Remains the fact that previous versions of vim didn't depend on these libs.

I think that is probably true.

I considered the possibility that previous versions of xvim/vim were compiled with a dependence on two libs that were included in a package of utilities for dealing with the xfs file system and we just didn't notice the dependence, but then I figured I was just trying too hard.

Anyway, I've got acl, attr and xvim all installed now, and they appear to be happy together. And that's what really counts.