![]() Google Desktop documentation seems to say. I don’t know what they’re supposed to do none of the The only apps that are targeted by these “mods” are Safari andĬamino. These “mods” are the code bundles injected by the SafariSearchResults.gmod, and SafariWebHistory.gmod. InsideĪre three bundles: CaminoGoogleDesktop.gmod, The second thing in this folder is a folder named Mods. Applications/ is just a springboard that launches this app. Is that this is the real updater app, and the one in Library/Application Support/Google/ weighs 2.8 MB. ![]() ![]() Applications/ folder weighs just 108 KB, the one here in What the difference is, but the Google Updater.app in the Is a second app bundle named “Google Updater.app”. Library/Application Support/Google/ - Two things here. Installing these things silently, is my own piece on Smart Work of the Devil?” TidBits article is a good introductionĪnd overview. Such files in your per-user Library folder.Ī discussion of why input managers are suspect is beyond the Google Updater does not give you the option to install The machine, and injects code into every Cocoa application you That means it is installed for all users on Googleĭesktop installs an input manager hack in the local domain Library/InputManagers/GoogleModLoader/ - Uh-oh. Results window when you tap Command-Command to invoke Google Software that shows you the sort of Quicksilver-ish query and Applications/ - Two apps are installed here, Googleĭesktop.app and Google Updater.app. That doesn’t do you any good before you run Google Updater, though. pkg installer packages, which means they leave behind BOM (“bill of material”) receipts in /Library/Receipts/, and so you can inspect them with the lsbom tool to see what was installed where. Update: It ends up that behind the scenes, Google Updater does its thing by downloading and installing software via standard. I ran the same command again after installation and searched for differences. Before the installation, I used the Unix ls command to generate a list of every file on the startup drive. So I installed Google Desktop on a test machine - an iMac G4 running Mac OS X 10.4.9. I won’t install software like this on my main machine without knowing everything that’s going to be installed. This matters with Google Desktop, because there are a lot of files, and they’re installed into some interesting - if not suspicious - locations. There’s no way to tell what files it’s going to install, or where. It’s a slick, easy-to-use piece of software, but alas, it lacks anything like the aforementioned Show Files feature of Apple’s installer. It also provides a simple one-button interface for uninstalling these apps. It doesn’t contain the software for any of these apps instead, it downloads the latest version when you choose to install or update one of them. This app is a meta installer for various Google Mac apps, including, as of today, Google Desktop, Earth, Notifier, and Picasa Uploader. Google Desktop is delivered using another new Google app, called Google Updater. A simple drag-and-drop installation wouldn’t work.īut Google doesn’t use Apple’s standard installer, either. I say “set” because Google Desktop is not just one piece of software, it’s a system with numerous components. I’ve only had time to give it a cursory examination, but it’s clearly a deep and complex set of software. Today, Google released Google Desktop for Mac, which, in a nutshell, is more or less a competitor to Spotlight. One of the nice features of Apple’s installer is the Show Files command in the File menu, which gives you a nice listing of everything the installer is going to install, before it happens. When that’s not possible or feasible, usually due to software that requires additional components, I much prefer when software uses Apple’s own installer tool. Uninstallation in such cases requires dragging the same file to the Trash. A disk image or zip archive that the user opens, then a single file (or bundle) that the user can drag to somewhere such as the Applications folder. Mac software is usually distributed in a way that encourages simple drag-and-drop installation. A Quick, Possibly Incomplete Guide to What Gets Installed by the Google Desktop Installer Wednesday, 4 April 2007
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |