- Performed a TOT 3.0.0 build. More stuff coming in...
- Struggling with 2.0 GD build. Turns out I was missing some CRs. Finally building!
- GDB Server build on Solaris is OK now but it fails on Linux. I suspect a packaging problem
- The portgd script has issues
Portgd Challenges
One of the problems with portgd is that the from CVS repository really needs to be set to HEAD because you want the latest but you're gonna pull the CRs by number and individual file revisions. This may cause problems sometimes (think ordering of CR numbers where pulling one CR overwrites a previous one in the wrong way. BTW This is why branching is good!)
Additionally portgd has a problem where the CR introduces new elements (Clearcase term - think new files and/or directories). When portgd attempts to cp the file to the to CVS repository it may fail because the parent directory did not previously exist and is not in the to CVS repository.
The portgd script can be updated to check to insure that each directory in the path of the file revision to be "ported" exists and if not then to create it and add it to CVS. It should also check to see if the file is new and again copy it but also add it to CVS.