Luckily, SpotlightFS continues to be developed. I went straight to the MacFuse Google Code page, and it just mentioned an unsupported Tiger version.

To install, I did:

0) Ensured I had MacPorts

1) Install:

port install spotlightfs

Failed for me, because I had the Tiger version hanging around still, so I de-installed it:

/Library/Filesystems/fusefs.fs/Support/uninstall-macfuse-core.sh

Then the next attempt running port install spotlightfs failed because of a ‘header not found error’. I did a port search fuse, and apart form the wonderfully named ‘libconfuse’, there was also a ‘libfuse’…assuming something wasn’t working with Darwin Ports’ dependency checking, I installed everything in this order:

port install libfuse
port install fusefs
port install libfuse
port install spotlightfs

Yes, I did libfuse twice…but just in case that’s significant, I offer it up anyway…didn’t seem to harm anything.

Can package systems resolve two-way dependencies?

E.g., say Pkg1 depends on the headers of Pkg2 to build, but Pkg2 depends on the libraries of Pkg1 to build… The correct answer is:

1. Install Pkg1 source
2. Install Pkg2 source (although at this point, it could happen before Pkg1)
3. Build Pkg1
4. Build Pkg2

I know sometimes you get the ‘devel’ package separate from the ‘run’ package, and that would mean it’s possible to do the above manually, but do package systems like DarwinPorts do it automatically?

The ‘System Events’ application is the key into system-wide GUI scripting. I’m going to make a GTD system that does context-sensitive clipping.

Need to implement double-dispatch: