Adopting porttools upstream?

Waitman Gobble uzimac at
Sun Jan 27 00:07:01 UTC 2013

Raphael Kubo da Costa <rakuco at> wrote ..
> Hi there,
> sergei@'s commit bit was taken into safekeeping years ago and porttool's
> project in SourceForge [1] has not seen any CVS commit for a long time
> as well.
> [1]
> Meanwhile, we've been patching ports-mgmt/porttools to keep up with our
> infrastructure changes and whatnot.
> I was thinking of integrating those fixes upstream and continuing the
> development somewhere else. skreuzer@ seems to have a fork on GitHub [2]
> with no previous history and some commits on top.
> [2]
> I, for one, ran devel/cvs2svn on the existing CVS history and converted
> it to git. The result looks OK and can be see in [3].
> [3]
> I'm not terribly interested in becoming porttools' upstream myself, but
> if others fail to jump aboard that could end up happening.
> Thoughts?
> _______________________________________________
> freebsd-ports at mailing list
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at"

Hi Raphael,

I forked, then svn update in /usr/ports and did 'make' in ports-mgmt/porttools, copied the merged files in 'work' and pushed the updates to, I believe that's the latest update?

Waitman Gobble
San Jose California USA

More information about the freebsd-ports mailing list