To get to a stage where projects and consolidations can deliver
directly into a repository, we need process. (Hold your applause.)
There are a couple of steps that a developer goes through to create a
new package. One of them is the package request to integrate (RTI).
I've included a blank copy of the current package RTI form below.
My first change will be to rename this to "request to package",
rather than package RTI, since we already have an RTI step on the
source side. But, if we want to keep this kind of step, we need to
revise this form--and reduce some of the duplication with other
stages of the process.
Please discuss. (Questions welcomed, too.) I can probably dig out
an example, if that would be helpful...
- Stephen
----
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 FORM
SUBMISSION DATE:
TARGET BUILD:
REQUESTER NAME/EMAIL:
ORGANIZATION:
DELIVERING C-TEAM:
REQUEST: [ ] new [ ] obsolete [ ] change
REQUEST SUMMARY:
PKG_ID:
PKG_DESC:
ARCH: [ ] x86 [ ] sparc
===========================================================================
TOTAL UNCOMPRESSED PKG SIZE in KB: ______
BASEDIR: [ ] / [ ] /var [ ] /opt [ ] /usr [ ] other
===========================================================================
IS PACKAGE NECESSARY FOR BOOTING? [ ] yes [ ] no
===========================================================================
LIST CONTENTS OF PACKAGE DEPEND FILE, OTHER DEPENDENCY INFO:
===========================================================================
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:
===========================================================================
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
===========================================================================
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):
===========================================================================
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=
--
[EMAIL PROTECTED] http://blogs.sun.com/sch/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
