What's new? | Help | Directory | Sign in
Google
igopher
Pocket Gopher - Install your iPod applications with an USB connection only!
  
  
  
    
Search
for
Updated Feb 10, 2008 by Scythal
AppTappBasics  
Basics of the AppTapp Installer

Introduction

The files used by the Installer are the following ones, where we note $user the default user on the iPod: root for firmware versions up to 1.1.2, mobile for firmware version 1.1.3 and possibly later versions.

The most important one, that you certainly don't want to lose, is LocalPackages.plist. It contains the list of the applications already installed on your iPod. If you remove this file, you will not be able to uninstall them, and probably not to update them either. It is possible to reconstruct this file manually but it could be a long and tedious task if you have many applications.

The second one that is worth keeping is PackageSources.plist, it contains the list of the repository sources you are currently using on the iPod. If you lose this file, you will have to re-enter the list of your favourite sources.

The two remaining files, RemotePackages.plist and TrustedSources.plist, are reconstructed by the Installer so they are not really important. The first one contains the list of the applications fetched from the different repositories at the last refresh, removing the file will force a refresh. The second is provided by the authors of the Installer, it is updated remotely to give the name of the trusted repositories. If the remote version is updated, or if the file is missing, Installer will fetch a new version.

How does Gopher work?

The Pocket Gopher scans the remote repositories whose list is in the PackageSources.txt file. When the user has chosen the applications and does an Export Script from the Files menu,

  1. Gopher builds a local repository local.plist in the export directory. It downloads all the necessary zip files, one for each application and renames them to app001.zip ... appxxx.zip to avoid name conflicts. The zip filenames are changed accordingly in local.plist.
  2. The export directory contents is transferred to the iPod.
  3. The original PackageSources.txt file of the Installer is saved in a backup directory /var/$user/Library/Installer/Backup/PackageSources.plist, unless it detects that file already.
  4. A new /var/$user/Library/Installer/PackageSources.plist file is generated, which points to the local repository just transferred.

So after an Export Script, the iPod Installer is in a local mode: it will ignore all your usual external repositories (http://repository.apptapp.com, http://conceitedsoftware.com/iphone and so on) and only show the applications you have exported.

You can install and update the applications as desired. This operation is of course much faster than when you go wireless. Once this is done, leave the Installer as usual, it will probably respring to show the modifications in SpringBoard (new icons, ...).

At this point, you have the choice to leave everything as is, for example if you don't intend to use remote repositories for the time being. Or you can restore the normal Installer mode, with the original sources: to do that, select Restore Sources in the Gopher iPod menu.

Something went wrong...

Then good luck. For now, you are basically on your own - see the big warning in the project home page? ;-)

Don't panic though, most problems won't need anything special from your part, it will typically be a non-existing zip file (faulty remote repository), a bad USB connection, or a problem while using the AppTapp Installer.

A few important remarks:

A log is kept in the program directory, it may help finding out what the problem is.

Note that a backup of the current LocalPackages.plist is made before each export in the backup directory on your PC, just where the Gopher.exe program is located. And it is very unlickely that your original LocalPackages.plist file has been destroyed on your iPod.

The same with PackageSources.plist:

In the worst case, you will have to re-enter the repository sources, but this really shouldn't happen.


Sign in to add a comment