Date: Fri, 06 Jun 2014 09:36:32 +0200 From: John Marino <freebsd.contact@marino.st> To: Jonathan Chen <jonc@chen.org.nz>, freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: Eclipse, git and source bundles Message-ID: <53916F80.4080509@marino.st> In-Reply-To: <CAJuc1zPsKoy6pXa4gFx6EwZ_YqRVQpxY_YOK-2hHb7_LU%2BaVpA@mail.gmail.com> References: <CAJuc1zPsKoy6pXa4gFx6EwZ_YqRVQpxY_YOK-2hHb7_LU%2BaVpA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53916F80.4080509>