efs-cpan... On Oct 5, 2010, at 3:22 PM, Phillip Moore wrote:
> I never did give up ownership of the AFS::Command CPAN modules, and I just > got the latest internal release from the guys at Morgan Stanley, since I > threatened to leave them in the dust if they didn't :-P > > The CPAN module's very old, and at version 1.7, and the version they sent me > is 1.12. Noone ever bothered to even consider updating the one on CPAN. > Sad, but soon to be corrected. > > I'm about to rewrite this code, significantly, and modernize it (well, modern > for my crude old school standards anyway), and I need a git repo to manage > it. Obviously, since it's one of the many things we'll be using in EFS, > seems reasonable to manage it along with the rest of our git repos. But what > should we call it? > > I see a couple of ways we can approach this generically, bearing in mind that > we are almost certainly going to be spawning more CPAN modules, so we need a > naming convention. We could create repos that are extension of either the > efs-perl or efs-cpan names, for example either of: > > efs-perl-afs-command > efs-cpan-afs-command > > would work for me. I don't personally think they need to be case sensitive > (i.e. efs-perl-AFS-Command), but I could be convinced otherwise. > > Opinions? Alternate suggestion? > > I need a new repo by weeks end for this, so speak now.... > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev _______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
