Alasdair Allan wrote:
>> 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.
I didn't mean to imply that the Starlink CVS repository would become the
master repository for your (or our) modules. I meant that every time you made
a release to CPAN or Starlink does a release or you put extra functionality in
that is required by other Starlink software (including ORAC-DR), then you'd do
a 'make dist' of Astro::Catalog and put the tarball in the Starlink CVS
repository.
Brad.
|