The typical development cycle is:
# generate base source packages for beta testing in ../tgz
admin --base --source --beta
# or delta source packages for beta testing in ../tgz
admin --source --beta
# make the local executables
admin --make
# check the make results
admin --results --failed | z
# run the regression tests
admin --test
# check the test results
admin --regress
# or
admin --results --failed --test | z
# or
rt -f - test.log/*
The typical packaging steps are:
# generate the locale message catalogs
admin --catalog
# generate base locale, source and binary packages in ../lcl, ../tgz
admin --base --save --locale --source --binary --official
# or delta locale, source and binary packages in ../lcl, ../tgz
admin --save --locale --source --binary --official
# generate astksh cygwin.i386 packages and --static-link standalone
admin --show --cygwin
# check the package generation results
admin --results --failed --generate | z
# make sure the source package(s) build in at least one empty vanilla environment
vanilla; bin/package read; bin/package make
# make sure the source package(s) build against the previous release
vanilla; export PATH=/prev/ast/bin:$PATH; bin/package read; bin/package make
# remove old binaries
admin --clean-binary
# check the generated binaries
admin --check
# update the internal web man pages
admin --wwwman
# update the internal web site with the latest release source/binaries
admin --post --base
# or update the internal web site with the latest release source
admin --post --base --source
# remove old download tarballs
admin --clean-download
To update the stage and external web sites:
# update the internal and stage www git repositories
admin --git
# surf http://silk.research.att.com/sw/download/
# check for internal seepage into /home/gsf/wwwfiles/download/@(make|test).*.html
# update the stage site
admin --stage
# update the public site
admin --public
# surf http://public.research.att.com/sw/download/
# mail ast-users # to announce the posting
admin --announce