Hello,

please see inline.

Stephen Hahn a écrit :
* Renaud Metrich <[EMAIL PROTECTED]> [2008-06-11 07:41]:
Hello,

I am in charge of providing TIPC to the OpenSolaris package repository by the november timeframe. TIPC is an open source project I already ported to Solaris and OpenSolaris (http://opensolaris.org/os/project/tipc/). I already created a set of SVR4 packages that are shipped with the source workspace.
I'm now wanting to create a set of corresponding IPS packages.

What do you think it is better to do:
1. publish the SVR4 packages to the repository directly by using the "pkgsend -s repository_url send
        SVR4_package_fmri" command
or
2. create dedicated IPS packages

It depends on (a) whether you need to deliver TIPC on non-image packaging systems,
      in which case use pkgsend (but use the import subcommand, not
      send), and

Well, the package will be delivered for Solaris 10 also in SVR4 format.
I read that package scripts from SVR4 packages were not run when package gets imported in IPS, in such case, how can I do to still have some script run automatically upon package installation (typically SMF related commands and driver installation commands)?

(b) what TIPC delivers and what kinds of dependencies it has.

TIPC has dependencies on Solaris base packages, such as SUNWcar SUNWkvm SUNWcsr SUNWcsu SUNWcsd SUNWcsl. Some TIPC packages (typically SUNWtipc-examples) has a dependency on the SUNWtipc package.


Also, I don't understand how to deal with package updates: TIPC is still in development and probably fixes from Linux'TIPC will be backported to the Solaris TIPC code, reusing the same release number.
Once created, is it possible to update a package content or not?
- If yes, no problem
- If no, how can I provide updates, it is by doing subreleases packages (ex: 1.7.5-1, then 1.7.5-2, etc.)? If so, what will happen when user gets the package? Will he get the latest subrelease?

  Yes, you can use subreleases (or just timestamp updates for typos),
  and yes, the user will get the latest subrelease.

OK.

cheers,

--
Renaud

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to