On Wed, Jan 24, 2001 at 04:12:26AM -0800, Ask Bjoern Hansen wrote:
> On Wed, 24 Jan 2001, Tony Smith wrote:
>
> > Name: P4::ClientApi
>
> Actually, that should probably be VCS::P4::Client or maybe even just
> VCS::P4.
>
> The other Version Control System modules are under VCS.
Kind of, the VCS::* tree has a VCS.pm module that's designed to
provide a common interface for VCS systems. So VCS is a 'framework'.
>From the docs:
: VCS is an API for abstracting access to all version control systems
: from Perl code. This is achieved in a similar fashion to the DBI suite
: of modules. There are "container" classes, VCS::Dir, VCS::File, and
: VCS::Version, and "implementation" classes, such as VCS::Cvs::Dir,
: VCS::Cvs::File, and VCS::Cvs::Version, which are subclasses of their
: respective "container" classes.
So I'd say go for VCS::P4... if you can/do/will support the generic
interface and it's sufficiently flexible for you.
Else, for example, stay with P4::* for 'native' access and, ideally,
also provide a simple VCS::P4 'shim' that provides a VCS.pm
compatibility layer.
Tim.
