What is the problem with ports PR reaction delays?

Aryeh Friedman aryeh.friedman at gmail.com
Sat Jan 25 17:30:53 UTC 2014

> By the way, this wasn't about switching to git (although that would be
> nice), this is about leveraging existing tools.
> One can very easily use git-svn bridge to push git changes into
> subversion. Or you can try to re-implement a patch queue based system
> yourself using a bunch of duct tape and bailing wire and likely get
> frustrated and either never complete it OR complete it and it's just not
> even half as good as git as a patch manager.
> Use the existing tools.
> I implore you to explore the idea of using existing tools to solve the
> problem, or at least solve a part of the problem, instead of trying to
> reinvent functionality that already exists

devel/tailor (which I maintain but never used) is designed to automatic
convert repos from one scm to an other this might be the best solution...
also I think the devel/aegis model of develop-->test-->review-->integrate
(which is built in by default but can be turned of or configured) might
help here (no need for changing tools unless we want to since most of this
is procedural) the basic model is:

1. One person develops
2. An other reviews
3. Yet an other intergates

I think the first 2 is what we need to focus on.   Namely when a new port
comes it is assigned a perm reviewer/integrator (aka comitter) and all
changes to that port from hence forth have that person as the assigned

Aryeh M. Friedman, Lead Developer, http://www.PetiteCloud.org

More information about the freebsd-ports mailing list