Stephen Hahn wrote:
To: XXX Subject: <OS> <registered_pkg_id> INTEGRATION REQUEST(NOTES: Packages must be registered at the registry.Package RTI must be received by the pkgteam on Monday of the week before the target build.)Nevada PACKAGE INTEGRATION REQUEST FORMSUBMISSION DATE: TARGET BUILD: REQUESTER NAME/EMAIL: ORGANIZATION: DELIVERING C-TEAM:
Is Organisation important and do we have C-teams (outside of Sun)? If not, can we simplify this to Os.O community name?
REQUEST: [ ] new [ ] obsolete [ ] change REQUEST SUMMARY:
I'm not sure I understand what is being asked for here, and if I'm confused, I'm sure others will be too.
PKG_ID:PKG_DESC:
As either Bart or Danek said earlier, can't we grab this from the pkg itself?
ARCH: [ ] x86 [ ] sparc
I thought arch went away because the repo contains content for all available architectures?
=========================================================================== TOTAL UNCOMPRESSED PKG SIZE in KB: ______BASEDIR: [ ] / [ ] /var [ ] /opt [ ] /usr [ ] other
I can see there might be value in this in planning a layout on disk, but is there any real value in having this information in the repo?
===========================================================================IS PACKAGE NECESSARY FOR BOOTING? [ ] yes [ ] no===========================================================================LIST CONTENTS OF PACKAGE DEPEND FILE, OTHER DEPENDENCY INFO:
Should come from the pkg itself really.
===========================================================================PRODUCT CLUSTER CHANGE(S): PRODUCT CLUSTER REQUEST: [ ] new [ ] obsolete [ ] modify PROD_CLUSTER_ID: PRODUCT CLUSTER NAME: PRODUCT CLUSTER DESCRIPTION: ADDED/DELETED PACKAGES: SPECIFY OTHER CHANGES, IF ANY:===========================================================================META_CLUSTER CHANGE(S): Cluster Entry Type: [ ] static [ ] dynamic If dynamic, specify dynamic test package and dynamic test(s): --------------------------------------------------------------------------- Use + or - to add/remove from ALL requested metaclusters. [ ] SUNWCXall (Entire distribution plus OEM support) [ ] SUNWCall (Entire distribution) [ ] SUNWCprog (Developer System Support) A justification is required for the following metaclusters: [ ] SUNWCuser (End-User System Support) [ ] SUNWCreq (Core System Support) [ ] SUNWCrnet (Reduced Networking System Support) [ ] SUNWCmreq (Minimal System Support -- USE WITH CAUTION) JUSTIFICATION/COMMENTS:
I thought I recalled a discussion about changing the clusters? What about distro's which aren't from Sun?
===========================================================================PRODUCT LAYOUT: Use + or - to add/remove from ALL requested areas.MINIROOT CHANGES:A justification is required for a package to be added to the miniroot due to space limitations on the solaris_1 CD. If possible please list the actual files from the package that are needed in the miniroot. [ ] CD/DVD Mini-Root ---------------------------------------------------------------------------MEDIA LOCATION:[ ] OS CD Product Area (solaris_{1-6}) [ ] ExtraValue/Early Access (solaris_6 media & solaris DVD) [ ] ExtraValue/CoBundled (solaris_6 media & solaris DVD) [ ] Language CD 1 (European/Japanese) [ ] Language CD 2 (Ko/zh/zh_TW) [ ] Source Packages (solaris_6 media & solaris DVD) --------------------------------------------------------------------------- FOR PACKAGES THAT CAN ONLY BE DISTRIBUTED TO THE US AND CANADA: [ ] Domestic Encryption Kit
I'm not sure this is applicable any more since the US lifted its restrictions on exporting software encryption technology.
=========================================================================== PACKAGE HISTORY FILE: (See http://solaris.sfbay/benet/Packaging/pkg_history.txt)If pkghistory file(s) will be delivered, show contents of the file(s) here.=========================================================================== DOCUMENTATION IMPACT: If documentation is impacted, list here.DOC(s): MANPAGE(s):
Is this relevant or important to anyone?
===========================================================================
FOR USE OF CENTERS DELIVERING G11N PACKAGES: If this is a localized package,
then list the value of the following macros in the pkginfo file:
SUNW_LOC=
SUNW_PKGLIST=
I don't think this information is valid for IPS is it?Given that there is certain information here which, if we definitely want it, can be obtained from the pkg, do we need to provide a script to generate this RTI?
Trev
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
