Commit Graph

10 Commits

Author SHA1 Message Date
Jacques Vidrine
f01c4343e0 Patch remotely exploitable libneon bugs after maintainer timeout.
PR:		ports/65754
Submitted by:	Frank Ruell <stoerte@dreamwarrior.net>
2004-04-30 16:04:38 +00:00
Ollivier Robert
aa6785e5a0 Put the right BUILD/RUN dependencies as gdiff/gpatch are both needed for
building and running tla.

Suggested by:	tobez
2004-03-01 22:20:03 +00:00
Ollivier Robert
8173766eb0 Update to tla 1.2, just released.
- SIZEify it
- added master sites (with conversion to main GNU site)
- use ${PRINTF}
- corrected WWW: in pkg-descr.
2004-02-27 13:05:01 +00:00
Joe Marcus Clarke
053fdb6a6b Bump PORTREVISION on all ports that depend on gettext to aid with upgrading.
(Part 2)
2004-02-04 05:21:48 +00:00
Ollivier Robert
b8b9d52e7b The diffutils package should be a BUILD_DEPENDS to satisfy the configure
script. Shut down a portlint warning too.

Committed because I did the previous update.

PR:		ports/60820
Submitted by:	Olivier Tharan <olive@oban.frmug.org>
2004-01-02 15:51:07 +00:00
Ollivier Robert
aa647df76c Update to 1.1-release.
OK'd by:	seanc (MAINTAINER)
2003-12-23 12:07:29 +00:00
Trevor Johnson
e99ceadaf6 Use the FIND and XARGS macros introduced in bsd.port.mk 1.391. 2003-11-13 14:45:08 +00:00
Sean Chittenden
a9120a9bdb Update tla to 1.1pre7.
Submitted by:	roberto
2003-10-13 20:51:13 +00:00
Sean Chittenden
12c7a2a2aa Update tla (C arch client) to use GNU's patch (gpatch).
Submitted by:	Curtis.Dunham@alltel.com
Obtained from:	arch-users mailing list
2003-08-26 21:38:09 +00:00
Sean Chittenden
0d3e362811 Add tla, an arch CLI written in C.
Arch is a really nifty revision control system. It's "whole-tree
changeset based" which means, roughly, that it can handle (with atomic
commits) file and directory adds, deletes, and renames cleanly, and
that it does branching simply and easily. Arch is also "distributed"
which means, for example that you can make arch branches of your own
from remote projects, even if you don't have write access to the
revision control archives for those projects.

This looks to be as close to an open source p4 replacement as one could
hope without being p4.  I'll go so far as to suggest that if this SCM
was employed by the BSD crowd, merging changes between dragonfly (post
source repo reorog), NetBSD, and OpenBSD would be radically less painful.
It is very possible that the dragonfly fork may not have happened under
the arch SCM development methodology, but if it did, at the very least it
would be possible to incorporate dillion's reorg work in a single patch
set, no cvs admin repo surgery needed.

WWW: http://arch.fifthvision.net/bin/view
2003-08-17 22:01:07 +00:00