Ports Search

Results 3,1113,120 of 5,623 for /devel/.(0.005 seconds)
devel/SVN-Access-0.10 (Score: 0.032514982)
Perl extension to manipulate SVN Access files
SVN::Access includes both an object oriented interface for manipulating SVN access files (AuthzSVNAccessFile files), as well as a command line interface to that object oriented programming interface (svnaclmgr.pl) which is in the examples/ directory.
devel/Sub-Uplevel-0.2500 (Score: 0.032514982)
Appear to run a function in a higher stack frame
Like Tcl's uplevel() function, but not quite so dangerous. The idea is just to fool caller(). All the really naughty bits of Tcl's uplevel() are avoided.
devel/SVN-Agent-0.04 (Score: 0.032514982)
Simple svn manipulation
This module provides regular svn operations on check out directory. It tries to do this in a simplest form possible. All operations are currently performed by running svn binary directly. Thus it is probably unportable. For a much more powerful way of working with svn repository see SVN::Client.
devel/SVN-Dump-0.06 (Score: 0.032514982)
Perl interface to Subversion dumps
An SVN::Dump object represents a Subversion dump. This module follow the semantics used in the reference document: * A dump is a collection of records (SVN::Dump::Record objects). * A record is composed of a set of headers (a SVN::Dump::Headers object), a set of properties (a SVN::Dump::Property object) and an optional bloc of text (a SVN::Dump::Text object). * Some special records (delete records with a Node-kind header) recursively contain included records.
devel/SVN-Dumpfile-0.13.107 (Score: 0.032514982)
Perl extension to access and manipulate Subversion dumpfiles
SVN::Dumpfile represents a Subversion dumpfile. It provides methods to read existing and write modified or new dumpfiles. It supports dumpfiles with the version number 1 - 3 but was written in a tolerant way to also support newer versions as long no major changes are made. This module is a OO redesign and generalisation of SVN::Dumpfilter v0.21. Newer versions of SVN::Dumpfilter are using it to access the input and output dumpfiles. The ability to create new dumpfiles sets it apart from the similar module SVN::Dump. The submodule SVN::Dumpfile::Node::Properties also allows the processing of Subversion revision property files (i.e. the files lying in the $REPOSITORY/db/revprops/ directory holding the author, date and log entry of every revision).
devel/Symbol-Util-0.0203 (Score: 0.032514982)
Additional utils for Perl symbols manipulation
Additional utils for Perl symbols manipulation
devel/SVN-Hook-0.28 (Score: 0.032514982)
Perl module for managing Subversion hook scripts
The SVN::Hook Perl module provides a programmable interface to manage hook scripts for Subversion.
devel/SVN-Hooks-1.31 (Score: 0.032514982)
Framework for implementing Subversion hooks
SVN-Hooks is a Perl framework for creating Subversion hooks. It comes with a bunch of plugins (actually, sub-modules of SVN::Hooks) that implement some of the most used standalone Subversion hooks available, such as pre-commit hooks for enforcing: - the log message format - property settings - the repository structure - restrictions on the modification of repository areas (e.g., /tags) - restrictions on filenames - the integration with ticketing systems It also comes with post-commit hooks for: - sending commit emails - updating configuration files in the server from changes made in the repository But as a framework, it can be extended to implement all types of hooks.
devel/SVN-Log-0.03 (Score: 0.032514982)
SVN::Log - Extract change logs from a Subversion server
SVN::Log retrieves and parses the commit logs from Subversion repositories.
devel/SVN-Look-0.41 (Score: 0.032514982)
Caching wrapper around the svnlook command
SVN-Look is a caching wrapper aroung the svnlook command. The svnlook command is the workhorse of Subversion hook scripts, being used to gather all sorts of information about a repository, its revisions, and its transactions. This script provides a simple object oriented interface to a specific svnlook invocation, to make it easier to hook writers to get and use the information they need. Moreover, all the information gathered buy calling the svnlook command is cached in the object, avoiding repetitious calls.