Ideally, there's nothing you should need to do to modify the source
tarball of the external package. We want the original, unmodified
source whenever possible. However, the name of the tarball is
-important, since the Condor build system itself makes assumptions
-about the name so that the =build_externals= script can download and untar
-the tarball for you (one less thing for your build-script to worry
-about for yourself). So, the source tarball must be
+important, since it's easier to update the build script with the new filename. So, the source tarball should be
named "=[name]-[version].tar.gz=" (and, needless to say, it must
be a real gzip'ed tar file). For example, "=krb5-1.2.7.tar.gz=".
-An important exception is that the =-p<number>= at the end of the version
+
+*TODO: May be out of date, the -p0 may be mandatory now* An important exception is that the =-p<number>= at the end of the version
is optional in the tarball name. For example, the tarball for external =krb5-1.2.7-p1= can be named =krb5-1.2.7.tar.gz= (the same tarball used for external =krb5-1.2.7=).
+*TODO: adesmet's edits end here*
+
{subsection: Putting the source tarball on the web server}
The source tarballs live on the web server parrot.cs.wisc.edu. They are synced periodically from the following directories on AFS at UW-CS:
