diff options
author | Ruslan Makhmatkhanov <rm@FreeBSD.org> | 2016-06-18 21:01:44 +0000 |
---|---|---|
committer | Ruslan Makhmatkhanov <rm@FreeBSD.org> | 2016-06-18 21:01:44 +0000 |
commit | 561a968c8b39f2c3aa994c72166c194e9d7c4f01 (patch) | |
tree | 0b79a6b2880a9a9258de2782b0fbb35a6d220c9e /devel/codeville | |
parent | ed289403dfe0c30801e3a7420658bff166475355 (diff) | |
download | freebsd-ports-561a968c8b39f2c3aa994c72166c194e9d7c4f01.zip |
devel/codeville: update to version 0.1.17
- update to 0.1.17
- actualize pkg-descr
- align patch file
- add NO_ARCH, while I'm here
PR: 210253
Submitted by: Chris Hutchinson <portmaster@bsdforge.com> (maintainer)
Diffstat (limited to 'devel/codeville')
-rw-r--r-- | devel/codeville/Makefile | 5 | ||||
-rw-r--r-- | devel/codeville/distinfo | 5 | ||||
-rw-r--r-- | devel/codeville/files/patch-setup.py | 6 | ||||
-rw-r--r-- | devel/codeville/pkg-descr | 25 |
4 files changed, 20 insertions, 21 deletions
diff --git a/devel/codeville/Makefile b/devel/codeville/Makefile index abe61343b95c..2f840fb67178 100644 --- a/devel/codeville/Makefile +++ b/devel/codeville/Makefile @@ -2,17 +2,16 @@ # $FreeBSD$ PORTNAME= codeville -PORTVERSION= 0.1.16 -PORTREVISION= 2 +PORTVERSION= 0.1.17 CATEGORIES= devel python MASTER_SITES= http://bsdforge.com/projects/source/devel/codeville/ -DISTNAME= Codeville-${PORTVERSION} MAINTAINER= portmaster@bsdforge.com COMMENT= Anarchic control version system without unnecessary re-merges LICENSE= BSD3CLAUSE +NO_ARCH= yes USES= python tar:xz USE_PYTHON= distutils autoplist diff --git a/devel/codeville/distinfo b/devel/codeville/distinfo index d8a777a2c6b3..0c8ad15c90ac 100644 --- a/devel/codeville/distinfo +++ b/devel/codeville/distinfo @@ -1,2 +1,3 @@ -SHA256 (Codeville-0.1.16.tar.xz) = b5cf02fa1846498c23c7d910b1b971793e173b00df9944593ed3c6357b9fdecb -SIZE (Codeville-0.1.16.tar.xz) = 70360 +TIMESTAMP = 1466283269 +SHA256 (codeville-0.1.17.tar.xz) = 8b7df400dec5b5d8eefe4f5d5de0b8aeff501736fb08b7094bb833d73079e901 +SIZE (codeville-0.1.17.tar.xz) = 70216 diff --git a/devel/codeville/files/patch-setup.py b/devel/codeville/files/patch-setup.py index d9918a556a33..0f478c65eec6 100644 --- a/devel/codeville/files/patch-setup.py +++ b/devel/codeville/files/patch-setup.py @@ -1,6 +1,6 @@ ---- setup.py.orig 2014-06-20 11:45:12.000000000 -0700 -+++ setup.py 2014-06-20 12:03:29.000000000 -0700 -@@ -44,6 +44,5 @@ +--- setup.py.orig 2016-06-13 06:31:53.378976000 -0700 ++++ setup.py 2016-06-13 06:32:11.276473000 -0700 +@@ -46,6 +46,5 @@ packages = ["Codeville", "Codeville/old"], ext_modules = plat_ext, diff --git a/devel/codeville/pkg-descr b/devel/codeville/pkg-descr index ec24d7f237c5..28c602abbd76 100644 --- a/devel/codeville/pkg-descr +++ b/devel/codeville/pkg-descr @@ -1,17 +1,16 @@ -Codeville is a distributed version control system. It began with a novel -idea for a merge algorithm and has grown from there. It is designed to -be easy to use and scale from small personal projects to very large -distributed ones. If you'd like to know why there is a need for new -merge algorithms, consider what the lead monotone developer had to say: +Codeville is a distributed Version Control System. It began with a novel +idea for a merge algorithm, and has grown from there. It is designed to +be easy to use, and scale from small personal projects, to very large +distributed ones. If you'd like to know why there's need for new merge +algorithms, consider what the lead monotone developer had to say: http://article.gmane.org/gmane.comp.version-control.monotone.devel/3264 -Codeville works by creating an identifier for each change which is -done, and remembering the list of all changes which have been applied -to each file and the last change which modified each line in each -file. When there's a conflict, it checks to see if one of the two -sides has already been applied to the other one, and if so makes -the other side win automatically. When there's an actual not -automatically mergeable version conflict, Codeville behaves in -almost exactly the same way as CVS. +Codeville works by creating an identifier for each change that is done, +and remembering the list of all changes which have been applied to each +file, and the last change which modified each line in each file. When +there's a conflict, it checks to see if one of the two sides has already +been applied to the other one, and if so, makes the other side win +automatically. When there's a non automatically mergeable version conflict, +Codeville behaves in almost exactly the same way as CVS. WWW: http://bsdforge.com/projects/devel/codeville/ |