svn commit: r417084 - in head/devel/codeville: . files
Ruslan Makhmatkhanov
rm at FreeBSD.org
Sat Jun 18 21:01:45 UTC 2016
Author: rm
Date: Sat Jun 18 21:01:44 2016
New Revision: 417084
URL: https://svnweb.freebsd.org/changeset/ports/417084
Log:
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 at bsdforge.com> (maintainer)
Modified:
head/devel/codeville/Makefile
head/devel/codeville/distinfo
head/devel/codeville/files/patch-setup.py
head/devel/codeville/pkg-descr
Modified: head/devel/codeville/Makefile
==============================================================================
--- head/devel/codeville/Makefile Sat Jun 18 20:54:44 2016 (r417083)
+++ head/devel/codeville/Makefile Sat Jun 18 21:01:44 2016 (r417084)
@@ -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 at bsdforge.com
COMMENT= Anarchic control version system without unnecessary re-merges
LICENSE= BSD3CLAUSE
+NO_ARCH= yes
USES= python tar:xz
USE_PYTHON= distutils autoplist
Modified: head/devel/codeville/distinfo
==============================================================================
--- head/devel/codeville/distinfo Sat Jun 18 20:54:44 2016 (r417083)
+++ head/devel/codeville/distinfo Sat Jun 18 21:01:44 2016 (r417084)
@@ -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
Modified: head/devel/codeville/files/patch-setup.py
==============================================================================
--- head/devel/codeville/files/patch-setup.py Sat Jun 18 20:54:44 2016 (r417083)
+++ head/devel/codeville/files/patch-setup.py Sat Jun 18 21:01:44 2016 (r417084)
@@ -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,
Modified: head/devel/codeville/pkg-descr
==============================================================================
--- head/devel/codeville/pkg-descr Sat Jun 18 20:54:44 2016 (r417083)
+++ head/devel/codeville/pkg-descr Sat Jun 18 21:01:44 2016 (r417084)
@@ -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/
More information about the svn-ports-head
mailing list