From tlarki at kckps.org Thu Feb 26 08:40:52 2009 From: tlarki at kckps.org (Thomas Larkin) Date: Thu, 26 Feb 2009 10:40:52 -0600 Subject: [Composer] chopping up packages Message-ID: <49A671B4.7141.0039.0@kckps.org> Hey everyone I totally knew how to do this over a year ago, but forgot and didn't document it. I want to create ilife08 in a package and chop it up into individual installs. Have an iLife required, then iMovies, iWeb, etc etc. So, if anyone knows the quick answer I would greatly appreciate it, thanks. ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/d4e748f6/attachment.html From sean.hansell at jwt.com Thu Feb 26 08:52:24 2009 From: sean.hansell at jwt.com (sean.hansell at jwt.com) Date: Thu, 26 Feb 2009 11:52:24 -0500 Subject: [Composer] chopping up packages In-Reply-To: <49A671B4.7141.0039.0@kckps.org> Message-ID: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc.

This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender.

-------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/3de452c0/attachment-0001.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 38992 bytes Desc: not available Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/3de452c0/attachment-0001.jpe From ERNSTCS at uwec.edu Thu Feb 26 09:25:46 2009 From: ERNSTCS at uwec.edu (Ernst, Craig S.) Date: Thu, 26 Feb 2009 11:25:46 -0600 Subject: [Composer] chopping up packages In-Reply-To: <3f13eedb-9428-4914-a487-a206e04e683d@list.jamfsoftware.com> Message-ID: You can also break out the other resources per application to keep it trimmer. So items in Library/Application Support/iDVD, iMovie,iPhoto, etc. The iDVD themes are about 800MB on their own. So Do what Sean has here, and if you want to go a step further bundle the support files with the individual applications as well. Craig E On 2/26/09 10:52 AM, "sean.hansell at jwt.com" wrote: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc. [cid:3318492346_1344093] This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/5c070296/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image.jpg Type: image/jpeg Size: 38992 bytes Desc: image.jpg Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/5c070296/attachment-0001.jpg From tlarki at kckps.org Thu Feb 26 09:38:46 2009 From: tlarki at kckps.org (Thomas Larkin) Date: Thu, 26 Feb 2009 11:38:46 -0600 Subject: [Composer] chopping up packages In-Reply-To: References: <3f13eedb-9428-4914-a487-a206e04e683d@list.jamfsoftware.com> Message-ID: <49A67F46.7141.0039.0@kckps.org> Thanks everyone It is still creating right now. I did a full iLife 08 install and then ran system update to get the updates and composer is now compiling everything into one package. I think want to split them up into separate packages afterward. I remember doing this last year, but that was a year ago... My memory is typically pretty good but I am failing on this scenario. Must be that I am finally getting old? ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:25 AM >>> You can also break out the other resources per application to keep it trimmer. So items in Library/Application Support/iDVD, iMovie,iPhoto, etc. The iDVD themes are about 800MB on their own. So Do what Sean has here, and if you want to go a step further bundle the support files with the individual applications as well. Craig E On 2/26/09 10:52 AM, "sean.hansell at jwt.com" wrote: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc. This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/d132a494/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 38992 bytes Desc: JPEG image Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/d132a494/attachment-0001.jpe From ERNSTCS at uwec.edu Thu Feb 26 09:55:50 2009 From: ERNSTCS at uwec.edu (Ernst, Craig S.) Date: Thu, 26 Feb 2009 11:55:50 -0600 Subject: [Composer] chopping up packages In-Reply-To: <49A67F46.7141.0039.0@kckps.org> Message-ID: Maybe I'm lazy, or someone has an opinion about it, but for anything that would normally update from Apple and an update server I package the base install and let software update do the rest with policies. =) But I can see wanting to make sure the most current stuff is there. I think iLife is an easier package to clean out the garbage anyway. Craig E On 2/26/09 11:38 AM, "Thomas Larkin" wrote: Thanks everyone It is still creating right now. I did a full iLife 08 install and then ran system update to get the updates and composer is now compiling everything into one package. I think want to split them up into separate packages afterward. I remember doing this last year, but that was a year ago... My memory is typically pretty good but I am failing on this scenario. Must be that I am finally getting old? ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:25 AM >>> You can also break out the other resources per application to keep it trimmer. So items in Library/Application Support/iDVD, iMovie,iPhoto, etc. The iDVD themes are about 800MB on their own. So Do what Sean has here, and if you want to go a step further bundle the support files with the individual applications as well. Craig E On 2/26/09 10:52 AM, "sean.hansell at jwt.com" wrote: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc. [cid:3318494150_1448799] This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/641b34c2/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: image.jpg Type: image/jpeg Size: 38992 bytes Desc: image.jpg Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/641b34c2/attachment-0001.jpg From tlarki at kckps.org Thu Feb 26 10:03:38 2009 From: tlarki at kckps.org (Thomas Larkin) Date: Thu, 26 Feb 2009 12:03:38 -0600 Subject: [Composer] chopping up packages In-Reply-To: References: <49A67F46.7141.0039.0@kckps.org> Message-ID: <49A6851A.7141.0039.0@kckps.org> Well, Can't I just make one package all together, then edit it in composer and chop it up into several ones? I think that is how I did it before hand. also, i like running the updates so I don't have to create more policies and have more policy logs in my JSS database. My database is already huge enough. If there is one thing I learned from the CCA training when I went, is it is best to do the leg work up front, instead of having a billion policies running in the after math. So, I can just create one giant package and use Composer's edit function to chop it up right? Then just add each individual one in Casper Admin and I am good to go? I think it is starting to come back to me, but I can't remember 100% so maybe I am not getting that old just yet. Thanks, ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:55 AM >>> Maybe I?m lazy, or someone has an opinion about it, but for anything that would normally update from Apple and an update server I package the base install and let software update do the rest with policies. =) But I can see wanting to make sure the most current stuff is there. I think iLife is an easier package to clean out the garbage anyway. Craig E On 2/26/09 11:38 AM, "Thomas Larkin" wrote: Thanks everyone It is still creating right now. I did a full iLife 08 install and then ran system update to get the updates and composer is now compiling everything into one package. I think want to split them up into separate packages afterward. I remember doing this last year, but that was a year ago... My memory is typically pretty good but I am failing on this scenario. Must be that I am finally getting old? ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:25 AM >>> You can also break out the other resources per application to keep it trimmer. So items in Library/Application Support/iDVD, iMovie,iPhoto, etc. The iDVD themes are about 800MB on their own. So Do what Sean has here, and if you want to go a step further bundle the support files with the individual applications as well. Craig E On 2/26/09 10:52 AM, "sean.hansell at jwt.com" wrote: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc. This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/cd7e2b6a/attachment.htm -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 38992 bytes Desc: JPEG image Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/cd7e2b6a/attachment-0001.jpe From paul.austin at wachovia.com Thu Feb 26 11:58:10 2009 From: paul.austin at wachovia.com (Paul Austin) Date: Thu, 26 Feb 2009 14:58:10 -0500 Subject: [Composer] Manual Diff Update Message-ID: Is there a way to manually update the Diff files with Composer 7? Our proxy server does not allow Composer to download updated diff files though our network. Thanks Paul Austin Wachovia Desktop Services From tlarki at kckps.org Thu Feb 26 13:16:12 2009 From: tlarki at kckps.org (Thomas Larkin) Date: Thu, 26 Feb 2009 15:16:12 -0600 Subject: [Composer] chopping up packages In-Reply-To: <49A6851A.7141.0039.0@kckps.org> References: <49A67F46.7141.0039.0@kckps.org> <49A6851A.7141.0039.0@kckps.org> Message-ID: <49A6B23C.7141.0039.0@kckps.org> OK, it looks like in Composer 7 there is a prebuilt environment tab that saves all of your packages and I am able to just create separate ilife installs off of that tab? Sorry for the hand holding today, ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Thomas Larkin" 02/26/09 12:03 PM >>> Well, Can't I just make one package all together, then edit it in composer and chop it up into several ones? I think that is how I did it before hand. also, i like running the updates so I don't have to create more policies and have more policy logs in my JSS database. My database is already huge enough. If there is one thing I learned from the CCA training when I went, is it is best to do the leg work up front, instead of having a billion policies running in the after math. So, I can just create one giant package and use Composer's edit function to chop it up right? Then just add each individual one in Casper Admin and I am good to go? I think it is starting to come back to me, but I can't remember 100% so maybe I am not getting that old just yet. Thanks, ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:55 AM >>> Maybe I?m lazy, or someone has an opinion about it, but for anything that would normally update from Apple and an update server I package the base install and let software update do the rest with policies. =) But I can see wanting to make sure the most current stuff is there. I think iLife is an easier package to clean out the garbage anyway. Craig E On 2/26/09 11:38 AM, "Thomas Larkin" wrote: Thanks everyone It is still creating right now. I did a full iLife 08 install and then ran system update to get the updates and composer is now compiling everything into one package. I think want to split them up into separate packages afterward. I remember doing this last year, but that was a year ago... My memory is typically pretty good but I am failing on this scenario. Must be that I am finally getting old? ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Ernst, Craig S." 02/26/09 11:25 AM >>> You can also break out the other resources per application to keep it trimmer. So items in Library/Application Support/iDVD, iMovie,iPhoto, etc. The iDVD themes are about 800MB on their own. So Do what Sean has here, and if you want to go a step further bundle the support files with the individual applications as well. Craig E On 2/26/09 10:52 AM, "sean.hansell at jwt.com" wrote: The quickest and easiest way to do this is to create the Composer package with all the apps installed, and simply pull out the Applications themselves, build and deploy them as seperate packages. Your required package would contain all the core files and inital preferences. Your other packages would simply contain /Applications/iPhoto.app/ and iWeb.app, etc. This transmission is intended solely for the person or organization to whom it is addressed and it may contain privileged and confidential information. If you are not the intended recipient you should not copy, distribute or take any action in reliance on it. If you believe you received this transmission in error please notify the sender. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/63f3c3fc/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 38992 bytes Desc: JPEG image Url : http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/63f3c3fc/attachment-0001.jpe From william.smith at merrillcorp.com Thu Feb 26 14:18:54 2009 From: william.smith at merrillcorp.com (Smith, William) Date: Thu, 26 Feb 2009 16:18:54 -0600 Subject: [Composer] Feature requests - Was chopping up packages Message-ID: On 2/26/09 3:16 PM, "Thomas Larkin" wrote: > OK, it looks like in Composer 7 there is a prebuilt environment tab that > saves all of your packages and I am able to just create separate ilife > installs off of that tab? I'm beginning to see a couple of feature requests here because Composer 7.0 isn't allowing me to do something I think would be intuitive for your problem. To do what you're asking, application suites are usually installed and then one major pre-built folder is created. It includes (using Adobe CS4 as an example): Applications Adobe Acrobat 9.0 Adobe Bridge CS4 Adobe Extension Manager CS4 Adobe Help Viewer 1.1 Adobe Illustrator CS4 Adobe InDesign CS4 Adobe Media Player.app Adobe Photoshop CS4 Library Application Support Color Sync Preferences Whatever else To divide this up into individual pre-built folders, you might create a "common" folder that includes all the /Library items (plus the Bridge, Extension Manager, Help Viewer, Media Player, etc.) and then individual pre-built folders for each application (Acrobat, Illustrator, InDesign and Photoshop). This dividing process takes place completely outside of Composer. I'd like to see it moved inside Composer. In Composer 7.x I'm essentially wanting to create "empty" packages (that's feature request #1) and then copy/move items using drag-n-drop from the larger package to the empty packages (that's feature request #2). Right now, Composer does not allow me to just create an empty package nor can I drag items between packages. -- bill William M. Smith, Technical Analyst MCS IT Merrill Communications, LLC w (651) 632-1492 m (612) 384-8572 From tlarki at kckps.org Thu Feb 26 14:27:25 2009 From: tlarki at kckps.org (Thomas Larkin) Date: Thu, 26 Feb 2009 16:27:25 -0600 Subject: [Composer] Feature requests - Was chopping up packages In-Reply-To: References: Message-ID: <49A6C2ED.7141.0039.0@kckps.org> That is exactly what I was running into. I was trying to get it to create a blank package so I could just drag in the essentials into one package, then drag in iMovie into the next, so on and so forth. Now, If I make a garage band package though off my prebuilt, and look at it's contents, I does seem to appear to have everything garage band needs but I am not sure. It grabs the application and everything out of /Library/Documentation/Applications/iPhoto and out of /Library/Receipts...? So I gotta chop this up outside of composer then drag it into Casper Admin? Which is not a huge deal I just want it done right the first time. ___________________________ Thomas Larkin TIS Department KCKPS USD500 tlarki at kckps.org blackberry: 913-449-7589 office: 913-627-0351 >>> "Smith, William" 02/26/09 4:18 PM >>> On 2/26/09 3:16 PM, "Thomas Larkin" wrote: > OK, it looks like in Composer 7 there is a prebuilt environment tab that > saves all of your packages and I am able to just create separate ilife > installs off of that tab? I'm beginning to see a couple of feature requests here because Composer 7.0 isn't allowing me to do something I think would be intuitive for your problem. To do what you're asking, application suites are usually installed and then one major pre-built folder is created. It includes (using Adobe CS4 as an example): Applications Adobe Acrobat 9.0 Adobe Bridge CS4 Adobe Extension Manager CS4 Adobe Help Viewer 1.1 Adobe Illustrator CS4 Adobe InDesign CS4 Adobe Media Player.app Adobe Photoshop CS4 Library Application Support Color Sync Preferences Whatever else To divide this up into individual pre-built folders, you might create a "common" folder that includes all the /Library items (plus the Bridge, Extension Manager, Help Viewer, Media Player, etc.) and then individual pre-built folders for each application (Acrobat, Illustrator, InDesign and Photoshop). This dividing process takes place completely outside of Composer. I'd like to see it moved inside Composer. In Composer 7.x I'm essentially wanting to create "empty" packages (that's feature request #1) and then copy/move items using drag-n-drop from the larger package to the empty packages (that's feature request #2). Right now, Composer does not allow me to just create an empty package nor can I drag items between packages. -- bill William M. Smith, Technical Analyst MCS IT Merrill Communications, LLC w (651) 632-1492 m (612) 384-8572 _______________________________________________ Composer mailing list Composer at list.jamfsoftware.com http://list.jamfsoftware.com/mailman/listinfo/composer -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090226/5cd79eb9/attachment.htm From william.smith at merrillcorp.com Thu Feb 26 15:20:08 2009 From: william.smith at merrillcorp.com (Smith, William) Date: Thu, 26 Feb 2009 17:20:08 -0600 Subject: [Composer] Feature requests - Was chopping up packages In-Reply-To: <49A6C2ED.7141.0039.0@kckps.org> Message-ID: On 2/26/09 4:27 PM, "Thomas Larkin" wrote: > So I gotta chop this up outside of composer then drag it into Casper Admin? > > Which is not a huge deal I just want it done right the first time. The "easy" but cumbersome way would be to let Composer make its monolithic package first. Then duplicate it four times so that you have a package for every application plus your "common" package (Right-click a Source in Composer to reveal in Finder.): GarageBand iPhoto iMovie iWeb Common Drag each package back into Composer and use its new "Convert to Source" feature to make a package. Rename the new package accordingly, delete everything but the needed contents and create a new package. Composer 7.0 now creates read-only/compressed packages, so package sizes will be at a minimum when done. The "out-of-Composer" but quick way would be to compose your source without creating a package. Then quit Composer and navigate to your working directory, which by default is within /Library/Application Support/JAMF/Sources, I believe. Check Composer's preferences to verify. You'll see something like: Library Application Support JAMF Sources iLife ROOT Scripts Settings Snapshots Create additional folders within Sources for each application: Library Application Support JAMF Sources iLife ROOT Scripts Settings Snapshots GarageBand ROOT Scripts Settings Snapshots iMovie ROOT Scripts Settings Snapshots iPhoto ROOT Scripts Settings Snapshots iWeb ROOT Scripts Settings Snapshots Within the ROOT folder of iLife (your package with everything), move each application into the ROOT folder of the new Source folder with its name. Recreate the folder structure as needed. Library Application Support JAMF Sources iLife ROOT Library Documentation More stuff Scripts Settings Snapshots GarageBand ROOT Applications GarargeBand.app Scripts Settings Snapshots iMovie ROOT Applications iMovie.app Scripts Settings Snapshots iPhoto ROOT Applications iPhoto.app Scripts Settings Snapshots iWeb ROOT Applications iWeb.app Scripts Settings Snapshots Launch Composer and it will see all the new sources. Make a package from each one. (I'm surprised I didn't find this in the KB on JAMF's website.) -- bill William M. Smith, Technical Analyst MCS IT Merrill Communications, LLC w (651) 632-1492 m (612) 384-8572 From mikael at dicom.se Fri Feb 27 03:55:16 2009 From: mikael at dicom.se (=?ISO-8859-1?Q?Mikael_L=F6fgren?=) Date: Fri, 27 Feb 2009 12:55:16 +0100 Subject: [Composer] Create Metapackage? Message-ID: <15B7042F-7DF0-4B5C-878F-BDDB61ECBBB3@dicom.se> Hi! I just bought Composer 7, i have used Iceberg to create package before and was trying Composer out. So my two first questions is, is there a way to create Metapackage in Composer 7? And in Iceberg my .pkg files had info string in Finder where i could se which version my .pkg has. But cant find that either in Composer. In Iceberg i set the info here: Iceberg->Display Information->Get Info String best regards Mikael From william.smith at merrillcorp.com Fri Feb 27 09:13:37 2009 From: william.smith at merrillcorp.com (Smith, William) Date: Fri, 27 Feb 2009 11:13:37 -0600 Subject: [Composer] Create Metapackage? In-Reply-To: <15B7042F-7DF0-4B5C-878F-BDDB61ECBBB3@dicom.se> Message-ID: On 2/27/09 5:55 AM, "Mikael L?fgren" wrote: > So my two first questions is, is there a way to create Metapackage in > Composer 7? > > And in Iceberg my .pkg files had info string in Finder where i could > se which version my .pkg has. > But cant find that either in Composer. > > In Iceberg i set the info here: > Iceberg->Display Information->Get Info String Hi Mikael! The JAMF folks could probably answer this one better than I can but I'd imagine this is currently by design. That's not to say they don't have plans to implement what you're wanting but rather this is the first revision of Composer in a long time and this newer version is in its infancy. Currently, I see that I cannot add a metapackage or a package to Composer and have it become part of a metapackage. I suggest contacting and providing them feature requests. -- bill William M. Smith, Technical Analyst MCS IT Merrill Communications, LLC (651) 632-1492 From sjhinding at isd194.k12.mn.us Fri Feb 27 14:00:38 2009 From: sjhinding at isd194.k12.mn.us (Sandy J. Hinding) Date: Fri, 27 Feb 2009 16:00:38 -0600 Subject: [Composer] Feature requests - Was chopping up packages In-Reply-To: References: Message-ID: HI! Chopping up packages: I confess I had not tried this in Composer 7... SO, for IWork, for instance, I made a Snapshot Package, all the way through "Build Package" button Quit Composer then went to /Library/Application Support/JAMF/Composer/Sources Made threee new folders (one for each app), named for each app Option Dragged "ROOT" from the original Source into each folder Go Back to Composer, where now you will see multiple Sources ready to package This rest can also be done in Composer, with the lovely Right-Clicks!! Deleted everything in those new ROOT folders except the APP inside of /Applications Removed the Applications from th original SOURCE folder (Leaving the Library Folder) Have a great Weekend! Sandy -------------- next part -------------- An HTML attachment was scrubbed... URL: http://list.jamfsoftware.com/pipermail/composer/attachments/20090227/f3352038/attachment.html From mikael at dicom.se Fri Feb 27 09:36:54 2009 From: mikael at dicom.se (=?ISO-8859-1?Q?Mikael_L=F6fgren?=) Date: Fri, 27 Feb 2009 18:36:54 +0100 Subject: [Composer] Create Metapackage? In-Reply-To: References: Message-ID: <96B69B9A-B20C-484A-A764-369F45F1D4B7@dicom.se> Thanks for the replay, i was hoping that JAMF folks is reading this but i will drop a support request as well! best regards Mikael 27 feb 2009 kl. 18.13 skrev Smith, William: > On 2/27/09 5:55 AM, "Mikael L?fgren" wrote: > >> So my two first questions is, is there a way to create Metapackage in >> Composer 7? >> >> And in Iceberg my .pkg files had info string in Finder where i could >> se which version my .pkg has. >> But cant find that either in Composer. >> >> In Iceberg i set the info here: >> Iceberg->Display Information->Get Info String > > Hi Mikael! > > The JAMF folks could probably answer this one better than I can but > I'd > imagine this is currently by design. That's not to say they don't > have plans > to implement what you're wanting but rather this is the first > revision of > Composer in a long time and this newer version is in its infancy. > > Currently, I see that I cannot add a metapackage or a package to > Composer > and have it become part of a metapackage. > > I suggest contacting and providing them > feature > requests. > > -- > > bill > > William M. Smith, Technical Analyst > MCS IT > Merrill Communications, LLC > (651) 632-1492 > > _______________________________________________ > Composer mailing list > Composer at list.jamfsoftware.com > http://list.jamfsoftware.com/mailman/listinfo/composer > -------------------------------------------------- Mikael L?fgren Dicom Datautveckling AB Box 6076, 102 32 Stockholm http://www.dicom.se Tele: 08-692 92 42 Mobil: 0709-52 92 42 Bes?ksadress: Norra Stationsgatan 61 --------------------------------------------------