mirror/freebsd-ports
1
0
Fork 0
mirror of https://git.FreeBSD.org/ports.git synced 2025-01-13 07:34:50 +00:00
Code Issues Releases Activity

- Add Piston:

Browse Source 
Piston is a utility that eases vendor branch management. This is
	similar to svn:externals, except you have a local copy of the files,
	which you can modify at will. As long as the changes are mergeable,
	you should have no problems.

	Piston has a similar purpose than svnmerge.py which you can find in
	the contrib/client-side folder of the main Subversion. The main
	difference is that Piston is designed to work with remote
	repositories.

	WWW: http://piston.rubyforge.org/
This commit is contained in:
Tim Bishop 2009-03-31 11:56:52 +00:00
parent 3149e59fcb
commit eca5054be0
Notes: svn2git 2021-03-31 03:12:20 +00:00 
svn path=/head/; revision=231382
4 changed files with 36 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
devel/Makefile
View File

@ -2573,6 +2573,7 @@
SUBDIR += rubygem-needle
SUBDIR += rubygem-open4
SUBDIR += rubygem-parsetree
SUBDIR += rubygem-piston
SUBDIR += rubygem-platform
SUBDIR += rubygem-ptreloaded
SUBDIR += rubygem-rake

21
devel/rubygem-piston/Makefile Normal file
View File

@ -0,0 +1,21 @@
# New ports collection makefile for: rubygem-piston
# Date created: 31 March 2009
# Whom: Tim Bishop <tdb@FreeBSD.org>
#
# $FreeBSD$
#
PORTNAME= piston
PORTVERSION= 1.4.0
CATEGORIES= devel rubygems
MASTER_SITES= RF
MAINTAINER= tdb@FreeBSD.org
COMMENT= Utility to manage local copies of Subversion repositories
USE_RUBY= yes
USE_RUBYGEMS= yes
RUBYGEM_AUTOPLIST= yes
PLIST_FILES= bin/piston
.include <bsd.port.mk>

3
devel/rubygem-piston/distinfo Normal file
View File

@ -0,0 +1,3 @@
MD5 (rubygem/piston-1.4.0.gem) = 8edc63db4de448fe411394dff0e64f32
SHA256 (rubygem/piston-1.4.0.gem) = 7d86d9e68dac5065cfb9160e24f073935dc85261a08f300e34e62b918537e230
SIZE (rubygem/piston-1.4.0.gem) = 16896

11
devel/rubygem-piston/pkg-descr Normal file
View File

@ -0,0 +1,11 @@
Piston is a utility that eases vendor branch management. This is
similar to svn:externals, except you have a local copy of the files,
which you can modify at will. As long as the changes are mergeable,
you should have no problems.
Piston has a similar purpose than svnmerge.py which you can find in
the contrib/client-side folder of the main Subversion. The main
difference is that Piston is designed to work with remote
repositories.
WWW: http://piston.rubyforge.org/