From owner-freebsd-ports@FreeBSD.ORG Sun Jan 27 00:07:01 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8F723DEB; Sun, 27 Jan 2013 00:07:01 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id E11B76EE; Sun, 27 Jan 2013 00:07:00 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r0R0706C036489; Sat, 26 Jan 2013 16:07:00 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r0R070qO036488; Sat, 26 Jan 2013 16:07:00 -0800 (PST) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: Re: Adopting porttools upstream? To: Raphael Kubo da Costa Message-Id: <1359245219.36483@da3m0n8t3r.com> X-Originating-IP: 50.197.134.190 X-Mailer: Usermin 1.510 In-Reply-To: <87r4l7ogss.fsf@FreeBSD.org> Date: Sat, 26 Jan 2013 16:07:00 -0800 (PST) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1359245220" Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 00:07:01 -0000 This is a multi-part message in MIME format. --bound1359245220 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Raphael Kubo da Costa 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] https://sourceforge.net/projects/porttools > > 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] https://github.com/skreuzer/porttools > > 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] https://github.com/rakuco/porttools > > 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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Hi Raphael, I forked https://github.com/rakuco/porttools, then svn update in /usr/ports and did 'make' in ports-mgmt/porttools, copied the merged files in 'work' and pushed the updates to https://github.com/waitman/porttools, I believe that's the latest update? -- Waitman Gobble San Jose California USA --bound1359245220--