"Jonathan Yu" <jonathan.i...@gmail.com> writes: > What I am looking for are the community's thoughts on such a module, > since it would really just be a large internal hash table with FourCC > codes mapped to descriptions (or, optionally, an SQLite database
A hint I got from someone (Andreas?) when I once thought about putting large datasets on CPAN (besides thinking twice if it's really neccessary at all) was: divide the packages into separate distributions, eg. Foo::Bar::Data and Foo::Bar::Everything::Else This way you don't spam the CPAN with the same data when the code changes, because Foo-Bar-Data keeps stable and the rest just depends on it. Kind regards, Steffen -- Steffen Schwigon <s...@renormalist.net> Dresden Perl Mongers <http://dresden-pm.org/> German Perl-Workshop 2009 <http://www.perl-workshop.de/en/2009>
