On Thu, 27 Jan 2005, Peter W. Draper wrote:
> Hi Mark,
>
> the export target was supposed to be used for creating an archive of the
> installed state of a package so that you could then just pass these out as
> updates or releases (along with all the other dependencies). The simplest
> use being just to untar/unzip the archives (possibly into an existing
> starjava tree) and off you'd go.
>
> In fact all the export targets are a little broken and need some work, the
> main reason being that they prepend the package name onto all the archive
> content, so cannot in fact be just unpacked. If Steve is going to do
> RPM/whatever package-level releases I guess this will have to change soon.
Another issue is the fact that file permissions - in particular the
execute bit - are currently lost when the zip/tar archives are built
(I seem to recall you can get round this for <tar> by not using explicit
<tarfileset> elements, but not for <zip>).
I could go through and fix the build files to the extent that the export
target works at least, but this would probably consist of just
commenting out things that cause trouble. In view of what you say
however, maybe it would make most sense if the nightly build doesn't
attempt the 'ant export' test until such time as we get round to
making this do something working/useful, when we can look at each one
individually and check it's doing something sensible.
I *think* (though haven't tested recently) that the export-full*
targets ought to work, so they can stay.
Agree?
Mark
--
Mark Taylor Starlink Programmer Physics, Bristol University, UK
[log in to unmask] +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/
|