Re: Bug in pcl-cvs mode

Okay, I updated the package index, and then ran list and install. However, this does not change the fact that XEmacs' package for pcl-cvs is 4 months out of date. My question remains: What is the expected modus operandi here for coping with the time lag between XEmacs packages as compared to the thing they are packages of? I'm generally a fan of the package as a distribution concept. However, in the face of ongoing development of various lisp components, it seems to me that I will be forced to basically defeat the packaging mechanism and resort to just installing lisp-vendor products into my own lisp tree and place that in front of the load path, just like I used to do before packages. The pcl-cvs package is a particular sore point in this resepct. I first reported a crippling bug in pcl-cvs diff mode in the 20.2 timeframe, and have been tracking XEmacs development ever since, primarily to get a fixed pcl-cvs mode. Pcl-cvs has basically been broken in XEmacs distributions for more than a year. I have friends using 19.15 specifically because of this unresolved problem with pcl-cvs having the "diff bug" in the 20 series. I'm testing the 21 betas specifically because of this bug. In the 21 betas the pcl-cvs mode has been significantly upgraded since the package used in the 19 and 20 strains, but it still has bugs, and the author tells me he has fixes available, but there are no packages for this. I imagine this problem transcends pcl-cvs, and is really something that users of all lisp packages are going to have to deal with. If lisp providers don't produce their releases as XEmacs packages, then it seems to me users are just going to have to circumvent the package mechanism. Or is there a larger plan here, of which I am unaware? Adrian Aichner writes: