From owner-svn-ports-head@freebsd.org Sun Sep 17 20:59:38 2017 Return-Path: Delivered-To: svn-ports-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B847E04C3B; Sun, 17 Sep 2017 20:59:38 +0000 (UTC) (envelope-from cs@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 66ECC6DBC3; Sun, 17 Sep 2017 20:59:38 +0000 (UTC) (envelope-from cs@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id v8HKxbE7050923; Sun, 17 Sep 2017 20:59:37 GMT (envelope-from cs@FreeBSD.org) Received: (from cs@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id v8HKxbw6050919; Sun, 17 Sep 2017 20:59:37 GMT (envelope-from cs@FreeBSD.org) Message-Id: <201709172059.v8HKxbw6050919@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: cs set sender to cs@FreeBSD.org using -f From: Carlo Strub Date: Sun, 17 Sep 2017 20:59:37 +0000 (UTC) To: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: svn commit: r450024 - in head/devel: . pijul X-SVN-Group: ports-head X-SVN-Commit-Author: cs X-SVN-Commit-Paths: in head/devel: . pijul X-SVN-Commit-Revision: 450024 X-SVN-Commit-Repository: ports MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Sep 2017 20:59:38 -0000 Author: cs Date: Sun Sep 17 20:59:37 2017 New Revision: 450024 URL: https://svnweb.freebsd.org/changeset/ports/450024 Log: Pijul is a version control system based on patches, that can mimic the behaviour and workflows of both Git and Darcs, but contrarily to those systems, Pijul is based on a mathematically sound theory of patches. Pijul was started out of frustration that no version control system was at the same time fast and sound: - Git has non-associative merges, which might lead to security problems. Concretely, this means that the commits you merge might not be the same as the ones you review and test. - Handling of conflicts: Pijul has an explicit internal representation of conflicts, a rock-solid theory of how they behave, and super-fast data structures to handle them. - Speed! The complexity of Pijul is low in all cases, whereas previous attempts to build a mathematically sound distributed version control system had huge worst-case complexities. The use of Rust additionally yields a blazingly fast implementation. WWW: https://pijul.org/ Added: head/devel/pijul/ head/devel/pijul/Makefile (contents, props changed) head/devel/pijul/distinfo (contents, props changed) head/devel/pijul/pkg-descr (contents, props changed) Modified: head/devel/Makefile Modified: head/devel/Makefile ============================================================================== --- head/devel/Makefile Sun Sep 17 20:49:16 2017 (r450023) +++ head/devel/Makefile Sun Sep 17 20:59:37 2017 (r450024) @@ -4054,6 +4054,7 @@ SUBDIR += picp SUBDIR += picprog SUBDIR += pig + SUBDIR += pijul SUBDIR += piklab SUBDIR += pinba_engine SUBDIR += pipestatus Added: head/devel/pijul/Makefile ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/pijul/Makefile Sun Sep 17 20:59:37 2017 (r450024) @@ -0,0 +1,26 @@ +# Created by: Carlo Strub +# $FreeBSD$ + +PORTNAME= pijul +PORTVERSION= 0.8.0 +CATEGORIES= devel +MASTER_SITES= https://pijul.org/releases/ + +MAINTAINER= cs@FreeBSD.org +COMMENT= Distributed version control system + +LICENSE= GPLv2 + +USES= cargo + +PLIST_FILES= bin/pijul \ + man/man1/pijul-show-dependencies.1.gz + +WRKSRC= ${WRKDIR}/${DISTNAME}/pijul +CARGO_CONFIGURE=no +INSTALL_TARGET= install-strip + +post-install: + ${INSTALL_MAN} ${WRKDIR}/${DISTNAME}/man/en/man1/pijul-show-dependencies.1 ${STAGEDIR}${PREFIX}/man/man1 + +.include Added: head/devel/pijul/distinfo ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/pijul/distinfo Sun Sep 17 20:59:37 2017 (r450024) @@ -0,0 +1,3 @@ +TIMESTAMP = 1505679001 +SHA256 (pijul-0.8.0.tar.gz) = 1d73114cc89ed87d9f6208312c578b240aeefa55ea41f1f595f62d71fd00f102 +SIZE (pijul-0.8.0.tar.gz) = 138427 Added: head/devel/pijul/pkg-descr ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/devel/pijul/pkg-descr Sun Sep 17 20:59:37 2017 (r450024) @@ -0,0 +1,21 @@ +Pijul is a version control system based on patches, that can mimic the +behaviour and workflows of both Git and Darcs, but contrarily to those systems, +Pijul is based on a mathematically sound theory of patches. + +Pijul was started out of frustration that no version control system was at the +same time fast and sound: + +- Git has non-associative merges, which might lead to security problems. + Concretely, this means that the commits you merge might not be the same as + the ones you review and test. + +- Handling of conflicts: Pijul has an explicit internal representation of + conflicts, a rock-solid theory of how they behave, and super-fast data + structures to handle them. + +- Speed! The complexity of Pijul is low in all cases, whereas previous attempts + to build a mathematically sound distributed version control system had huge + worst-case complexities. The use of Rust additionally yields a blazingly fast + implementation. + +WWW: https://pijul.org/