Hello Benjamin, Thanks for your advice to break dependency loop. Now I have binary package sbt-launch_0.10.0, and source package sbt_0.10.1 which is built by the former. The problem now is sbt can not download libraries from the internet while on Launchpad farm. It seems Launchpad build machines are not connected to the outer network, and it definitely breaks the build process.
So what should I do now to overcome the limitation? On Wed, 2011-06-29 at 20:28 +0200, Benjamin Drung wrote: > Am Mittwoch, den 29.06.2011, 21:56 +0400 schrieb Sergey Ukustov: > > Hi all, > > > > I'm Sergey Ukustov, 23 yo, from Volgograd, Russia. > > PhD student and Scala+js :) developer. Have scratched the surface of the > > Debian packaging. > > > > I would like to know how to package simple-build-tool. It is a build > > tool like make or maven but configurable in Scala. It is distributed as > > a jar file sbt-launcher.jar. Users usually create "sbt" wrapper command > > for java -jar sbt-launcher.jar. The problem is sbt is built using early > > version of itself. It means one must have sbt-launch.jar of the version > > v0.7 for example to build sbt-launch.jar v0.10. > > > > Please, tell me what is the best practice to handle this kind of > > (self-dependent when building) programs. > > Starting packaging with simple-build-tool is not the easiest way to get > started. > > You need to break the build dependency loop somehow. Either build > simple-build-tool without itself (for example, by writing an ant file) > or package an old version of simple-build-tool that can be built without > itself. > Sincerely yours, Sergey Ukustov.
signature.asc
Description: This is a digitally signed message part
-- Ubuntu-motu-mentors mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu-mentors
