Michael Kifer writes:
>>>>> "KJ" == Kyle Jones <of Mon, 03 May
1999 19:13:59 PDT> writes:
KJ> Michael Kifer writes:
>> > > Viper requires some functions defined in vc-hooks.el
>> > Can this dependency be removed? It is a rather non-obvious
>> > dependency, much like EFS requiring VM, and it would a be a good
>> > thing if the linkage could be made to go away.
>> It needs to know whether a file is under version control.
>> For this, it uses vc-backend. I could never understand why vc-hooks.el is
>> such a bad thing to depend on.
KJ> I think you can assume that if vc-backend is not a valid function
KJ> (vc-hooks not loaded), then for your purposes the file is not
KJ> under version control.
This assumes that the file being queried has been already visited (so vc
would be loaded). But sometimes viper queries the file even if it is not
Hmmm. How about using (featurep 'vc-hooks) before forcing the
load of VC? If (featurep 'vc-hooks) you can assume the user
has chosen to use VC.
KJ> We don't load vc-hooks by default because VC is not
KJ> liked and once vc-hooks is loaded, you're pretty much stuck with
I heard this many times, but personally never experienced any problems. I
use both VC and pcl-cvs, and can't see where the two clash.
Are there any other problems?
I don't know (or care really) why some people don't like VC. I
remove package dependencies on general principle. Your package,
your call. If you don't want to change it, then we need to list
VC as a runtime dependency in the viper package spec, if such a
thing is possible.