Hate to bust that theory, but i first noticed that BSD package was gutted sometime in 2008. Here is my (Leopard 10.5.8) rendition of that item:
$ ls -laR /Library/Receipts/BSD.pkg
-rw-r--r-- 1 root admin 0 Nov 29 2007 /Library/Receipts/BSD.pkg
It's an empty file!!!
I don't know how you got that. On
my 10.5.8 volume, I have:
ls -lOde /Volumes/Savanna/Library/Receipts/BSD.pkg
drwxrwxr-x 3 root admin - 102 Jun 14 2006 /Volumes/Savanna/Library/Receipts/BSD.pkg
du -sh /Volumes/Savanna/Library/Receipts/BSD.pkg
3.2M /Volumes/Savanna/Library/Receipts/BSD.pkg
On my 10.6.2 volume I have:
ls -lOde /Library/Receipts/BSD.pkg
-rw-r--r-- 1 root admin - 0 Sep 9 18:33 /Library/Receipts/BSD.pkg
So you're right about it leaving an empty file rather than an empty folder. The date (Sep 9) is the day I installed 10.6.0.
I first noticed this while digging into a complaint from a fellow MUG member that her Jaguar DURP was refusing to even look at her Snow Leopard system, despite never having balked at repairing permissions on her Tiger and Leopard systems. I read her the riot act about not using old repair utilities on new systems and the converse in DURP's case (and didn't hide my feelings on DURP in general), but I was curious to know why Jaguar's DURP, which obviously never checked versions before, was suddenly doing it now.
BSD.pkg was the one thing that the Snow Leopard installer changed that Jaguar's DURP would have looked at.
