Willie Walker wrote: > Karen Tung wrote: > >> What Jack described is probably the easiest thing for you to do right now. >> If you want to "automate" it and utilize the checkpointing feature, you can >> write a little finalizer script yourself that does the copying of your >> modified >> files to the pkg_image area. Then, put this finalizer script as the >> first one >> in the finalizer script list. >> > > Awesome. Makes perfect sense. At this point, my finalizer script can > also use the pkg command to remove/replace/add packages, right? It > *seems* like everything is in place at that point and that the distro > constructor already has some python tools I could use to accomplish this. > Yes. But be careful about the repository it pulls from. At the end of the population of the pkg_image area, we set the default authority to the standard opensolaris one. You'll want to make sure you override this.
Jean > If this can be done, the distro constructor should just about have what > I need, I think, and no enhancement requests would be needed. :-) > > Thanks! > > Will > > >> In order to do the way of adding packages you mentioned below, we probably >> need 2 package lists, and check pointing between each adding each list. >> It could be a useful feature, but we definitely won't have time for this >> for the Nov release. Please file an enhancement request in bugzilla so >> we can keep track of it, and if we found that a lot of people want to do >> it, >> we can implement it in the future. >> >> Thanks, >> >> --Karen >> >> >> >> Jack Schwartz wrote: >> >>> Hi Will. >>> >>> Here's the easiest way: If you to change a file delivered by a >>> package, just add the changed file directly to the pkg_image area, >>> then run steps 2+. Once you get things the way you like them, move >>> the stuff you changed to where you build your package. Then rebuild >>> the package, add to your repo, and do one (hopefully) final complete >>> run including the IPS bringover from your repo. >>> >>> Hope that helps, >>> Jack >>> >>> Willie Walker wrote: >>> >>> >>>> Hi All: >>>> >>>> Sorry...one more question. :-) I'm trying to find a way to >>>> eliminate the step to grab aaallllll the packages for the system when >>>> all I really want to do is just change or add a couple packages. >>>> >>>> For example, maybe I just want to rebuild SUNWslim-utils or add >>>> SUNWgnome-a11y-speech-espeak. From a prior run, something has >>>> already pulled all the other packages off my IPS and put them in the >>>> package image. Since that takes sooooooooo long, I'd like to avoid >>>> repeating that step if I can. >>>> >>>> So...what I'm looking for is a way to: >>>> >>>> 1) Populate the package image with everything from the standard IPS >>>> files and make a checkpoint. >>>> >>>> 2) Start with the checkpoint. >>>> >>>> 3) Create/modify the packages I want to play with. >>>> >>>> 4) Put my new packages in the package image, removing/replacing old >>>> ones if necessary. >>>> >>>> 5) Build my iso and test. >>>> >>>> 6) Go back to #2. >>>> >>>> I could accomplish this, the load on the IPS server would be greatly >>>> reduced and I would be able to prototype/test much faster. >>>> >>>> Is this possible today? I played with checkpointing and it seems to >>>> work (yeah!), but I'm not sure how to update the package image >>>> without just replacing it entirely. >>>> >>>> Will >>>> >>>> _______________________________________________ >>>> caiman-discuss mailing list >>>> caiman-discuss at opensolaris.org >>>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>>> >>>> >>> _______________________________________________ >>> caiman-discuss mailing list >>> caiman-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >>> >>> > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
