Home Forums Software InstaDMG InstaUp2Date docs

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #375720
    AllanMarcus
    Participant

    Hi,

    Sorry for the barrage of questions, but I’m just getting into InstaDMG (and lovin’ it!).

    The docs for InstaUp2Date are a little vague. I’ve gotten the vanilla and development catalogs to work, and now I want to add third party software. Couple of questions:

    1) Where to I put the dmg or pkg files? Can I create a new folder in the main InstaDMG folder and put there there? I would rather not add them to the Caches/InstaUp2DateCache folder (I would like to keep them separate from the apple updates.

    2) The sample catalog in the repo refers to the “autoUpdateCache folder or one of the InstaDMG numbered folders”. Is that documented somewhere?

    3) How can I use “InstallerChoices.xml” for the packages I want to manage through InstaUp2Date?

    Thanks,

    Allan

    #375763
    larkost
    Participant

    1) The packages that you produce go into: InstaDMG->InstallerFiles->InstaUp2DatePackages. The ones that InstaUp2Date downloads for you (from the vanilla.catalog file for example) get put in InstaDMG->Caches->InstaUp2DateCache.

    2) Ya, that is a little confusing. I just checked in a change the new lines are:
    [code]# The <> can be one of the following:
    # name of a .pkg file in the InstaUp2DatePackages folder in InstallerFiles
    # http: reference to be downloaded (a flat-file .pkg, a .dmg or a .zip of a folder)[/code]

    3) The easiest way is to wrap the installer and the InstallerChoices.xml file in a .dmg. At one point you could just put them in a folder, but that code dropped away (I think), and the major revision that is in my head does not have to worry about that.

    #378240
    Allister Banks
    Participant

    Hey all,

    I’m moving on from the semi-unfinished state of the InstaDMG doc to work on this, as I’ve finally decided to incorporate InstaUp2Date in my workflow.
    1. I’m hoping the InstallerChoices.xml can stay loose because I make images including pre-serialized site license software for different clients, and I’m hoping to reference the same .xml. Can anyone provide feedback on this and a a few other InstaUp2Date questions?

    2a. Can a catalog file reference a pkg/dmg located on an AFP fileshare?
    2b. How about on another locally mounted volume?

    3. If not, are randomly-named subfolders allowed, so I can reference ./instadmg/installerFiles/InstaUp2DatePackages/Client1/AccountingPkgs ?

    4. Could someone please post the relevant parts of where one catalog file references another?

    Thanks,

    Allister Banks POINT http://www.pointconsultants.comĀ  646.502.4708 368 Broadway Ste. 303 New York, New York 10013

    #378241
    larkost
    Participant

    2 a and b) The files can be anywhere on the filesystem, but InstaUp2Date has no ability to open AFP shares, so they have to already be mounted before it gets there. I am not against adding this ability, but it is going to take a lot of work, and there are security concerns with storing passwords.

    3. I need to look over that code a bit to remember it. I know that just names work (as long as the files are in the proper folder), but I need to look at things a bit better, and maybe re-write that section.

    4. Simply a line like:

    include-file:

    You can have as many spaces in front of it as you want, it really does not affect anything.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.

Comments are closed