Timothy Schmidt wrote: Hi Tim,
Thanks for the info. I do not see the DONE directory you mentioned below: bash-3.2$ ls -al /net/benet/benet/S10*/RE/pkg_registry/DONE /net/benet/benet/S10*/RE/pkg_registry/DONE: No such file or directory bash-3.2$ ls -al /net/benet/benet/S10*/RE/pkg_registry | grep DONE Thanks. colin > >> Hi, >> >> I created and registered a package cal SUNWlogotate. This has been >> registered with wolfman.sfbay.sun.com. >> From code review I was informed that I actually needed 2 packages - 1 >> for user and another for root because >> my User command installs a file in /etc. >> >> So, I was told that I should have a package name: >> >> SUNWlogrotateu >> SUNWlogrotater >> >> Does this mean that I register this 2 new packages and delete >> SUNWlorotate? >> > > Yes > > > >> In forms that ask for package name which one is the >> package name or do I use both? >> > > I'm going to assume (based on your wiki link below) that you are > talking about an RE pkg RTI form similar to the S10U6 example one here: > > file:///net/benet/benet/S10U6/RE/forms/pkg_rti.form > > The choice as to whether or not to use one form for more than one > pkg depends on how closely aligned the packages information is. > > The bottom line is whether or not you can CLEARLY and EASILY > describe the information aligned with the package or packages > you are submitting the form for. If it seems confusing to you, > then it probably will to the reader. So in some cases it's better > to use more than one RTI form for clarity's sake. > > >> So, I will have to delete the OLD package name SUNWlogrotate. >> >> Another question. >> > > You have quite a lot of "questions" below. :) > > To start with there are installation level METACLUSTERS which you > do NOT create. They are listed in RTI section shown as follows: > ------------------------------------------------------------------- > 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) > -------------------------------------------------------------------- > > When the solaris DVD is built, a list of meta clusters and the pkgs aligned > with them is created. When the end user installs the DVD he/she > chooses a METACLUSTER to install. So, depending on how you > fill out this section, your pkg(s) will or won't be installed by the > user based on their METACLUSTER selection. Put a "+" sign next to > each METACLUSTER you want to install your pkg(s). If you > are *LATER* trying to remove an entry from a METACLUSTER you would > use the "-" sign. > > So, if you use the RTI form for TWO or more packages, you can see that > *IF* they are to be installed in *DIFFERENT* metaclusters it *MAY* be > wiser to use two forms! Again, just make sure the RTI is easy to > understand. > > When do you use one RTI for 2 or more packages? > Let's say you have mulitple (2 or more) packages that always > (or almost always) are used or installed together. In that case > you can create a PRODUCT CLUSTER. This allows you to use the > PRODUCT CLUSTER name instead of having to list each package every time > you want the "group" of packages to be referenced. So, where applicable, > in the METACLUSTER section you would again at a "+" sign. > > Now, in the more complicated scenario where you want to use the > PRODUCT CLUSTER in *most* of the METACLUSTERs, but you only want to > have SUNWlogrotater in the SUNWCreq METACLUSTER, you would do this: > > NOTE: Assume you made a PRODUCT CLUSTER called *SUNWCmyprodcluster* > that contains SUNWlogrotateu and SUNWlogrotater. > ----------------------------------------------- > Use + or - to add/remove from ALL requested metaclusters. > > [+] SUNWCXall (Entire distribution plus OEM support) > SUNWCmyprodcluster > [+] SUNWCall (Entire distribution) > SUNWCmyprodcluster > [+] SUNWCprog (Developer System Support) > SUNWCmyprodcluster > > A justification is required for the following metaclusters: > > [+] SUNWCuser (End-User System Support) > SUNWCmyprodcluster > [+] SUNWCreq (Core System Support) > SUNWlogrotater > [ ] SUNWCrnet (Reduced Networking System Support) > [ ] SUNWCmreq (Minimal System Support -- USE WITH CAUTION) > ----------------------------------------------- > > As far as PRODUCT CLUSTER (also simply called CLUSTER) naming, > for the most part, just make sure it is unique and makes sense. > > The best thing to do is to look at existing examples. > Look in /net/benet/benet/S10*/RE/pkg_registry/DONE for previously > submitted RTIs. > > I hope this helps. > > ..tim > > >> I was also told that because I actually have 2 packages, I need to to >> something with Cluster/Meta Cluster etc. I believe there is a naming >> convention. Can someone please provide direction on what I need to get >> done - pointers etc. >> >> This is what I copied from >> http://wikihome.sfbay.sun.com/spe-re/Wiki.jsp?page=Annotated_rti: >> >> PRODUCT CLUSTER CHANGE(S): >> If you are checking in a set of (one or more) packages that are a >> functional unit, these should be grouped into a >> product cluster. >> >> PRODUCT CLUSTER REQUEST: [ ] new [ ] obsolete [ ] modify >> Mark with 'X' one of these only if you are adding or making cluster >> modifications. >> PROD_CLUSTER_ID: >> The cluster ID is selected from the base name of the set of packages >> that are part of it. For example, if a new abc >> driver is being added with 3 new packages (SUNWabc, SUNWabcr, SUNWabcu), >> the cluster ID is best described by the abc >> name itself, so it would be called SUNWCabc (where the C designates a >> cluster). >> >> PRODUCT CLUSTER NAME: >> The cluster name is a one-line title for the cluster. It can be the same >> as what is in the NAME field of the cluster's main >> package's pkginfo file. >> >> PRODUCT CLUSTER DESCRIPTION: >> Up to 256 characters can be used here, but sometimes the PROD_CLUSTER >> NAME used above works well with this. >> If more words are needed to accurately describe it, they are welcome here. >> >> ADDED/DELETED PACKAGES: >> Specify the package(s) affected. To be precise, use '+' or '-' as the >> case maybe. To facilitate processing, keep separate >> the add (+) request from the remove (-) request. They may be entered in >> two separate lines under this section. >> >> SPECIFY OTHER CHANGES, IF ANY: >> Provide or specify other changes as appropriate. >> >> Do I have to register the Cluster name anywhere? Or is it just needed here? >> >> What is a Meta Cluster? >> > >
