Path: csiph.com!feeder.erje.net!1.us.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!newsfeed.straub-nv.de!news.mixmin.net!aioe.org!bofh.it!news.nic.it!robomod
From: Mehdi Dogguy <mehdi@dogguy.org>
Newsgroups: linux.debian.maint.java,linux.debian.bugs.dist
Subject: Re: Packaging sbt
Date: Wed, 06 Jan 2016 02:00:02 +0100
Message-ID: <qNKCe-299-5@gated-at.bofh.it>
References: <qNBpg-4ua-25@gated-at.bofh.it> <qNBSh-4Kz-1@gated-at.bofh.it>
Old-Return-Path: <mehdi@dogguy.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.5.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Approved: robomod@news.nic.it
Lines: 20
Organization: linux.* mail to news gateway
Sender: robomod@news.nic.it
Xref: csiph.com linux.debian.maint.java:8697 linux.debian.bugs.dist:706561

Hi,

On 05/01/2016 16:32, Emmanuel Bourg wrote:
> The "easiest" solution is probably to start with a non-free sbt package
> containing a prebuilt version of sbt, and then upload in main a sbt
> package depending on itself with the prebuilt sbt removed. I would use
> only one sbt package, instead of sbt-bootstrap in non-free and sbt in main.
> 

Note that you can very much include a working sbt binary in the source
package and use it the bootstrap sbt. The only condition that we must
respect is to not ship that binary in the package, but ship the built
binary only. This is done for many packages: OCaml for its bootstrap
and most probably ghc (didn't check tbh). Also, compiling gcc requires
a gcc. :-P

My 2 cents,

-- 
Mehdi