Brad Cavanagh wrote:
> Tim Jenness wrote:
>> Next up is PERLMODS. Should we upload untarred versions of the CPAN
>> modules to CVS?
I used to do thing for eSTAR, I've now stopped doing it, there is just
too much overhead to maintain the tree, I ended up having several
hundred modules that had to be kept up to date.
I currently carry a directory of tarballs, and have a csh script to
untar and rebuild each package. When a new version of the module turns
up I replace to previous version with the newer version. This works
okay, but isn't great.
> Would we have to include all of the dependencies as well? Some of them
> (like Astro::Catalog -- I'm assuming that that's going to have to be
> put in the Starlink CVS repository at some point, considering ORAC-DR
> uses it now)
As things currently stand, I wouldn't be very happy about loosing
control of the master version of Astro::Catalog into the Starlink CVS.
> have a hell of a lot of dependencies. I know Al carries around those
> dependencies in his own CVS repository, but I don't know how
> up-to-date he keeps it.
Some of the dependancies aren't easily buildable automatically and have
to be manually tweaked and build time, mostly those that wrap Fortran
or C. The dependancy tree isn't currently up to date, and worryingly
for Astro::Catalog is growing quickly. I'm going to try and reengineer
the interface soon to try and make things a bit more optional, as it's
all rapidly getting out of hand.
Al.
|