Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 5 Jun 2007 23:33:45 +0200 (CEST)
From:      Martin Horcicka <martin@horcicka.eu>
To:        FreeBSD-gnats-submit@FreeBSD.org
Cc:        pav@FreeBSD.org
Subject:   ports/113392: New port: devel/py-lock_file Lock file manipulation
Message-ID:  <200706052133.l55LXjva003519@bar.horcicka.eu>
Resent-Message-ID: <200706052210.l55MA4sX002263@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         113392
>Category:       ports
>Synopsis:       New port: devel/py-lock_file Lock file manipulation
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 05 22:10:03 GMT 2007
>Closed-Date:
>Last-Modified:
>Originator:     Martin Horcicka
>Release:        FreeBSD 6.2-RELEASE-p1 i386
>Organization:
>Environment:
System: FreeBSD bar.horcicka.eu 6.2-RELEASE-p1 FreeBSD 6.2-RELEASE-p1 #0: Fri Mar 23 23:18:43 CET 2007 root@bar.horcicka.eu:/usr/src/sys/i386/compile/CUSTOM i386


	
>Description:
	A Python module for lock file manipulation.
>How-To-Repeat:
	
>Fix:

	

--- py-lock_file.shar begins here ---
# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#	/usr/ports/devel/py-lock_file
#	/usr/ports/devel/py-lock_file/distinfo
#	/usr/ports/devel/py-lock_file/Makefile
#	/usr/ports/devel/py-lock_file/pkg-descr
#	/usr/ports/devel/py-lock_file/pkg-plist
#
echo c - /usr/ports/devel/py-lock_file
mkdir -p /usr/ports/devel/py-lock_file > /dev/null 2>&1
echo x - /usr/ports/devel/py-lock_file/distinfo
sed 's/^X//' >/usr/ports/devel/py-lock_file/distinfo << 'END-of-/usr/ports/devel/py-lock_file/distinfo'
XMD5 (lock_file-1.0.tar.gz) = e22d72e9adc7b690954b40118b58b7cf
XSHA256 (lock_file-1.0.tar.gz) = 1bf525dfce21ad10c4f121e4ec5ade36da90c3d97a7336ed91c7f65ebaa576f8
XSIZE (lock_file-1.0.tar.gz) = 2162
END-of-/usr/ports/devel/py-lock_file/distinfo
echo x - /usr/ports/devel/py-lock_file/Makefile
sed 's/^X//' >/usr/ports/devel/py-lock_file/Makefile << 'END-of-/usr/ports/devel/py-lock_file/Makefile'
X# New ports collection makefile for:	lock_file
X# Date created:		5 June 2007
X# Whom:			Martin Horcicka <martin@horcicka.eu>
X#
X# $FreeBSD$
X#
X
XPORTNAME=	lock_file
XPORTVERSION=	1.0
XCATEGORIES=	devel python
XMASTER_SITES=	http://martin.horcicka.eu/python/lock_file/
XPKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
X
XMAINTAINER=	martin@horcicka.eu
XCOMMENT=	Lock file manipulation
X
XUSE_PYTHON=		2.4+
XUSE_PYDISTUTILS=	yes
X
X.include <bsd.port.mk>
END-of-/usr/ports/devel/py-lock_file/Makefile
echo x - /usr/ports/devel/py-lock_file/pkg-descr
sed 's/^X//' >/usr/ports/devel/py-lock_file/pkg-descr << 'END-of-/usr/ports/devel/py-lock_file/pkg-descr'
XLock files are used on Unix-like systems as a means of synchronization among
Xprocesses. Only one process can hold a lock file. Other processes that want to
Xacquire it have to wait until it is released by the holder.
X
XIn this module the lock file is implemented as an empty regular file,
Xexclusively locked using fcntl.flock. The file is removed when it is to be
Xreleased.
X
XWWW: http://martin.horcicka.eu/python/lock_file/
END-of-/usr/ports/devel/py-lock_file/pkg-descr
echo x - /usr/ports/devel/py-lock_file/pkg-plist
sed 's/^X//' >/usr/ports/devel/py-lock_file/pkg-plist << 'END-of-/usr/ports/devel/py-lock_file/pkg-plist'
X%%PYTHON_SITELIBDIR%%/lock_file.py
X%%PYTHON_SITELIBDIR%%/lock_file.pyc
X%%PYTHON_SITELIBDIR%%/lock_file.pyo
END-of-/usr/ports/devel/py-lock_file/pkg-plist
exit
--- py-lock_file.shar ends here ---


>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200706052133.l55LXjva003519>