Thanks for the response Shawn. Please see inline.. On Tue, Oct 21, 2008 at 1:51 AM, Shawn Walker <[EMAIL PROTECTED]>wrote:
> ramanujan oops wrote: > >> Hi, >> >> I'm currently looking forward for some help in porting my SVR4 >> application package to opensolaris, hence this mail! >> >> I have read through few blogs and was able to run my own depot server and >> publish a sample package into that server and install it on the host too. >> However, I have a few open questions for which I'm looking for answers. >> Please take a look and see if you can help me out here.. >> >> * Even if I had not started the depot server on my host, is >> http://pkg.opensolaris.org my default depot repository ? >> > > The default repository is going to be the same as the default authority > currently set for your pkg client. In the case of an OpenSolaris 2008.05 > install, pkg.opensolaris.org is your default repository. Can anyone publish their package into pkg.opensolaris.org? Lets say I distribute my IPS package to the customer for their use and I plan to do it by giving the clients a script which publishes my application package files to their corresponding repository server. Going by this case, say if every one is using "pkg.opensolaris.org" as their repository server, then it means the pkg.opensolaris.org will have more than one copy of same package in its repository. Is this intended? Or Am I missing something? > > > * What happens to the post/pre install and post/pre remove scripts >> which were used in SVR4 package? I have a huge chunk of code with >> those scripts at present.. >> > > They are gone. Instead, any work performed by them must either be done by > using the new actions that ips provides for a package's manifest (such as > file, mode, group, etc.), by a SMF service delivered with the package, or by > a single-use script delivered with the package that gets executed by SMF. I don't have enough hands-on in SMF service.Can you point me to materials which explains SMF for IPS? My preinstall and postinstall scripts did a few preliminary checks on the user environment and also it added cron jobs. I assume that I will be able to achieve this through SMF. But there are pre and post remove scripts which cleans up the crons that the application created. Will I be able to achieve this functionality as well in IPS version using SMF? > > * For client side applications, how do we release these packages? I >> understand that the current SVR4 sun application packages are just >> distributed via the SDLC site. But, with the IPS package, its not >> simply distributing a package. To develop a package, one needs >> depot server..Does it mean that I will have to distribute all the >> files in a directory structure and provide the customer with >> scripts to generate the package (say, the pkg.depot include file >> option??). My application is currently available for download as a >> SVR4 package via the SDLC site. Now, after I port the package to >> IPS form, how do I distribute it? >> > > The only way to "release" packages currently is through a network > repository; no on-disk format currently exists though that will be done at > some point in the future. > > Cheers, > -- > Shawn Walker >
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
