h1. Introduction
Jyri J. Virkki
Computers are great at repetitively checking the same things over and over, so I prefer to let them do it. Which leads to my preference to automate away anything repetitive. The SFW integration process relies on a seemingly endless number of details which are mostly hidden away in the memory of those who've done it long enough.
I'd like to see much of this automated to reduce the load on people and to reduce errors. This wiki page is for tracking details which should really be automated. I'll update this as we discover them during the course of web stack component integrations. Feel free to add more.
h1. Automation Task List
* Package dependencies - the 'depend' file needs to list correct package dependencies. This is currently done visually but should be automated. Bug 6626852 references http://xserver.sfbay/~alanc/check-deps.pl, investigate. [DependsScript|http://wikis.sun.com/display/WebStack/DependsScript] also provides the same information.
* pkginfo 'classes' - verify that it includes the exact list of classes used (often cut'n' paste leads to errors here)
* package makefile 'DEPEND' - if pulling files from common_files, list properly vs. the files in SCCS here
* prototype_* files - check the actions (if any) are correctly packaged
* apache integration had in prototype_com "e none etc/apache2/2.2/original/httpd.conf" but "e" requires some action (renamenew, renameold) can't be none. this IS caught by a validation script, but one that runs only after putback to gate. this kind of thing needs to be validated prior to putback.
* prototype_* 'manifest' - manifest file uses manifest action, it doesn't need to be included but still referenced in 'classes' (6625975 for detail)
* RPATH & RUNPATH validation, see 6625381
* apache integration removed SUNWapch2* -> SUNWapch22*. A few other packages (some of SUNWsvn*) depended on SUNWapch2u. This is caught by validation only after integration.
* Package SUNWapch22r should not package files in /var/run
Jyri J. Virkki
Computers are great at repetitively checking the same things over and over, so I prefer to let them do it. Which leads to my preference to automate away anything repetitive. The SFW integration process relies on a seemingly endless number of details which are mostly hidden away in the memory of those who've done it long enough.
I'd like to see much of this automated to reduce the load on people and to reduce errors. This wiki page is for tracking details which should really be automated. I'll update this as we discover them during the course of web stack component integrations. Feel free to add more.
h1. Automation Task List
* Package dependencies - the 'depend' file needs to list correct package dependencies. This is currently done visually but should be automated. Bug 6626852 references http://xserver.sfbay/~alanc/check-deps.pl, investigate. [DependsScript|http://wikis.sun.com/display/WebStack/DependsScript] also provides the same information.
* pkginfo 'classes' - verify that it includes the exact list of classes used (often cut'n' paste leads to errors here)
* package makefile 'DEPEND' - if pulling files from common_files, list properly vs. the files in SCCS here
* prototype_* files - check the actions (if any) are correctly packaged
* apache integration had in prototype_com "e none etc/apache2/2.2/original/httpd.conf" but "e" requires some action (renamenew, renameold) can't be none. this IS caught by a validation script, but one that runs only after putback to gate. this kind of thing needs to be validated prior to putback.
* prototype_* 'manifest' - manifest file uses manifest action, it doesn't need to be included but still referenced in 'classes' (6625975 for detail)
* RPATH & RUNPATH validation, see 6625381
* apache integration removed SUNWapch2* -> SUNWapch22*. A few other packages (some of SUNWsvn*) depended on SUNWapch2u. This is caught by validation only after integration.
* Package SUNWapch22r should not package files in /var/run