Right now we pull the build infrastructure out of CVSDude, with the Solaris/
directory of each package tarred up into a SOLARIS-<package>-<version>
tarball; these are uploaded and hosted on bionicmutton. So far that has been
the easiest way to make our packages buildable through specfiles, I think.
What we *do* get, regrettably often, is mismatches between the specfile and
the Solaris tarball -- things get fixed in one place, not in another, or an
updated Solaris tarball isn't uploaded (bear in mind this thing also contains
the patches to be applied to the pristine sources, so it's important). I'd
like to guard against this in future by adding ",<rev>" to the tarball name;
this would at least offer us the possibility of noticing breakage sooner.
The idea would be: when you update patches or stuff in dude, bump src_rev
(this is the independent specfile revision for the given source version of the
package) to force a new download of a new tarball; this will also show off
when you've forgotten to upload a newly rolled tarball from Dude.
Comments?
Patches for this are quite trivial; it's a matter of adding it to the one
Source line in common.spec and then fixing the tools to create properly named
tarballs.
--
Adriaan de Groot - KDE Quality Team, KDE-Solaris
- http://www.englishbreakfastnetwork.org/
- http://solaris.kde.org/
