From owner-freebsd-ports@FreeBSD.ORG Fri Jun 6 07:37:10 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6C240ED7 for ; Fri, 6 Jun 2014 07:37:10 +0000 (UTC) Received: from shepard.synsport.net (mail.synsport.com [208.69.230.148]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 455B82FDE for ; Fri, 6 Jun 2014 07:37:09 +0000 (UTC) Received: from [192.168.0.22] (unknown [130.255.19.191]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by shepard.synsport.net (Postfix) with ESMTP id BEDF243B4A; Fri, 6 Jun 2014 02:36:52 -0500 (CDT) Message-ID: <53916F80.4080509@marino.st> Date: Fri, 06 Jun 2014 09:36:32 +0200 From: John Marino Reply-To: marino@freebsd.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Jonathan Chen , freebsd-ports Subject: Re: Eclipse, git and source bundles References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2014 07:37:10 -0000 On 6/6/2014 09:31, Jonathan Chen wrote: > Hi, > > There's an outstanding PR which brings Eclipse up to 4.3.2: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=188659 > > Unfortunately, this has been rejected as it clones a git-repo in order > to run a build. I've had a look around the 'Net, and I can't seem to > find a source download for the Eclipse 4.3.2. The older bundles can be > found at: http://download.eclipse.org/technology/linuxtools/eclipse-build/ > ; but this appears for have been discontinued for later versions. > > What should be the course of action if the upstream does not provide a > source-bundle and expects a developer to check out the version from > git in order to build a proejct? One solution is roll your own tarball and host it. You'd just clone the repo, rsync it to remove all the .gitignore / .git SVN CVS directories, tar it and upload it. Then you become the trusted source. :) I do this sometimes when I need the top of a repo between releases. John