The zc.lockfile package provides a basic portable implementation of
interprocess locks using lock files. The purpose if not specifically to lock
files, but to simply provide locks with an implementation based on file-locking
primitives. Of course, these locks could be used to mediate access to other
files. For example, the ZODB file storage implementation uses file locks to
mediate access to file-storage database files. The database files and lock file
files are separate files.
RGBDS (Rednex Game Boy Development System) is a free assembler/linker
package for the Game Boy and Game Boy Color. It consists of:
* rgbasm (an assembler)
* rgblink (a linker)
* rgbfix (a checksum/header fixer)
* rgbgfx (a PNG-to-Game Boy graphics converter)
This is a fork of the original RGBDS which aims to make the programs
more like other UNIX tools.
carton is a command line tool to track the Perl module dependencies for
your Perl application. Dependencies are declared using cpanfile format,
and the managed dependencies are tracked in a cpanfile.snapshot file,
which is meant to be version controlled, and the snapshot file allows
other developers of your application will have the exact same versions
of the modules.
Menlo::Legacy is a package to install Menlo::CLI::Compat which is a
compatibility library that implements the classic version of cpanminus
internals and behavios. This is so that existing users of cpanm and API
clients such as Carton, Carmel and App::cpm) can rely on the stable
features and specific behaviors of cpanm.
This way Menlo can evolve and be refactored without the fear of breaking
any downstream clients, including cpanm itself.
Menlo is a backend for cpanm 2.0, developed with the goal to replace
cpanm internals with a set of modules that are more flexible, extensible
and easier to use.
Parse::PMFile - parses .pm file as PAUSE does
The most of the code of this module is taken from the PAUSE code as of
April 2013 almost verbatim. Thus, the heart of this module should be
quite stable. However, I made it not to use pipe ("-|") as well as I
stripped database-related code. If you encounter any issue, that's most
probably because of my modification.
This module doesn't provide features to extract a distribution or parse
meta files intentionally.
This module provides a common library for working with a variety of CPAN
index services. It is intentionally minimalist, trying to use as few
non-core modules as possible.
The CPAN::Common::Index module is an abstract base class that defines a
common API. Individual backends deliver the API for a particular index.
* [ Mark Haber ]
* Fix hours_since for git fake bare repos
* [ Tom Hoover ]
* Fix 'no defined update command error' in example config
* [ Pavel Nakonechnyi ]
* More meaningful names for temporary files
* [ Paul Wise ]
* Mitigate vulns caused by git code execution (CVE-2018-7032)
* Migrate from ack-grep to ack
* More reliable output supervision
* Improve the status output for CVS
* Improve the git-cvs extension
* Allow prepending commands to existing commands
* Allow for fallback to default commands
* Add support for caching command output
* Add shell extension to maintain a repo status cache
* Add graph, remote, upgrade extensions
* git registration improvements
* webcheckout: prefer https transport
pkgsrc changes:
- Rename directory to myrepos, catching up with package name change years ago
PyHamcrest is a framework for writing matcher objects, allowing you to
declaratively define "match" rules. There are a number of situations where
matchers are invaluable, such as UI validation, or data filtering, but it is in
the area of writing flexible tests that matchers are most commonly used.
When writing tests it is sometimes difficult to get the balance right between
overspecifying the test (and making it brittle to changes), and not specifying
enough (making the test less valuable since it continues to pass even when the
thing being tested is broken). Having a tool that allows you to pick out
precisely the aspect under test and describe the values it should have, to a
controlled level of precision, helps greatly in writing tests that are "just
right." Such tests fail when the behavior of the aspect under test deviates
from the expected behavior, yet continue to pass when minor, unrelated changes
to the behaviour are made.
This project provides a database of test results which can be used as part of
developer workflow to ensure/check things like:
* No commits without having had a test failure, test fixed cycle.
* No commits without new tests being added.
* What tests have failed since the last commit (to run just a subset).
* What tests are currently failing and need work.
Test results are inserted using subunit (and thus anything that can output
subunit or be converted into a subunit stream can be accepted).
