##osx-server

I mean, no, you don't need to recreate those plists

Those should only be needed whenever there's a new base installer, so a major new "product"

hmmm... I mean the update packages.

like now, there are new updates of Photoshop, Illustrator... etc. So, I have to recreate new .ccp files and recreate new product-plists? No?

using aamporter (Tim Sutton)

Shouldn't need to. If you're looking for the updates that are available for a .ccp file that reflects installing, say, Photoshop CC 2015 I'd think you'd just re-run aamporter when the new updates are released.

hmm... but if you take a look inside a .ccp file, there you can see the updates for product.

Nick_ZWG: I'm just wondering how I can integrate the suppression mechanisms (bash scripts) with a pkg that does the system upgrade

And if you don't recreate the .ccp, then how will aamporter find out new updates?

Orphis_ : You should read the documentation createOSXInstallPkg

It allows you to incorporate other packages, such as the ClearRegistration package I linked ealrier

If you want to apply configurations as part of the upgrade process, that's a great way to do it

Bit_: aamporter queries Adobe. For example, aamporter says "I have this .ccp file that says that it installs Photoshop CC 2015--do you have any updates for that 'channel' of software?" Adobe responds "The Photoshop CC 2015 update channel includes Photoshop CC 2015 15.2.2 and Camera RAW 9.3.3".

aamporter querys Adobe directly?????? THAT's what I wanted to know.

Nick_ZWG: Then I need to create a pkg that runs the script

I thought, that aamporter parses only the content of the .ccp file (where you can see all the product-updates inside

so I thought, that I had to use CCP again to recreate updated .ccp files and reparse them qith aamporter

The --build-product-plist task is a one-time thing you do per installer

Orphis_: Right, or find someone else who has done so already.

Nick_ZWG: Looking for that right now :)

hmmm... so how can I recreate and update the update-packages for munki?

just rerun aamporter on the product-plists --minkiimport ?????

that's magic

and it'll reimport into munki newer update-packages? WOW!

I have to try this tomorrow. It's almost midnight here

I do a quick demo of it as part of my MacSysAdmin 2015 talk

I've seen (5 times) :) your presentation form macadmins.se :)

yes, this one!

Ok - I know I went through it fast, but that's really all there is

I've seen this. But it was not clear how to update the updates

if ever there were new updates

Just re-run aamporter with the same list of products you gave it last time

WOW!

you're a magician!

(Harry)

Tim Potter

urawzrdarry

Thanks tvsutton !

so just have to re-run aamporter --build-product-plist blaCC.ccp --munki-update-for blaCC ?

and it'll make new plists which I reimport with munkiimport_cc_installers.py ?

and munki will get NEW update-packages?

that's magic. I'll try tomoroow @ work!

any news on managing AcrobatDC like this?

tvsutton: sorry to disturb you again. There's a much more important question: How can I get the Adobe CC Desktop App into Munki if there's a new version?

building a pacakge containing only the Core components with CCP works, but it itsn't recognised with aamporter

That one you might have to just build with CCP

you can't

If you want an updated CCDA, just build a pkg with no application payload in CCP

aamporter is to provide updates to Adobe products

you could build a pacakge which contains only the "Core Compnents" This one MIGHT contain the Adobe CC Desktop App. But aamporter refuses it.

aamporter doesn't need to worry about that

You could just import it directly into Munki.

how that?

The package you produce from CCP that has only "Core Components" can be imported directly into Munki. aamporter won't find updates for it, because it's not really a "CC" product

it's more of a side effect

ah - you mean, my "Core Components" pgk? using munkiimport directly?

Yep.

WOW!

I'll try that

Aamporter is a way to incorporate updates from Adobe's normal update channels into munki without having to rebuild them via CCP each time.

aamporter isn't necessary to import Adobe CC packages into Munki at all.

I was just wondering, why munkiimport_cc_installers refuses this pkg

no, it's not necessary, but it helps a lot because it makes batch import.

Just guessing here, but my guess is that it doesn't follow the same structure as other CC packages.

yup - THAT message is popping up

"Core components" pretty much the "stuff" that aamporter avoids packaging in the first place.

I'm even not sure, if this "Core omponents" pkg contains the Adobe CCDesktop App

It does, that's part of the core components

But one of the advantages of aamporter is that you don't need to include that in every single update pkg that comes out of aamporter

(it is included with every. single. update pkg that comes out of CCP)

or should I bettter download the CC Desktop app directly and import this one in munki?

I'd create a new CCP pkg that doesn't include any applications. Import that pkg into Munki.

WAT? So, if I build an update-pkg for Bride (which contains Camaer-RAW, etc..) it'll contain a newer Adobe CC Desktop App?

yes

^^ yes, that's waht I menat with "core components" pkg

Thanks, I'll try tomorrow. Have a nice night (or day... wherever you are on our small planet) :)