We've yet to receive an explanation of the rationale for this package being installed by default (or even for its very existence). It's been causing major usability problems for almost 3 years now. It's unfathomable that it's installed on Ubuntu server VM images!
This is exactly the kind of problem that puts people off using Ubuntu and drives them, bewildered, back to Windows, knowing nothing except that "Linux is slow as molasses compared to Windows; randomly it will get so slow I can't even watch a video on YouTube!"
Here are the packages that depend on or recommend apt-xapian-index:
Still affecting Raring.
We've yet to receive an explanation of the rationale for this package being installed by default (or even for its very existence). It's been causing major usability problems for almost 3 years now. It's unfathomable that it's installed on Ubuntu server VM images!
This is exactly the kind of problem that puts people off using Ubuntu and drives them, bewildered, back to Windows, knowing nothing except that "Linux is slow as molasses compared to Windows; randomly it will get so slow I can't even watch a video on YouTube!"
Here are the packages that depend on or recommend apt-xapian-index:
$ apt-cache rdepends apt-xapian-index backend- aptcc
apt-xapian-index
Reverse Depends:
software-center
muon-installer
muon-discover
muon
synaptic
packagesearch
packagekit-
muon-installer
muon-discover
muon
goplay
fuss-launcher
ept-cache
software-center
python-apt
aptitude
What does it take to get something done about this? Should I upload patches to these packages that removes it from their dependencies?