Last modified: 2013-06-05 10:31:19 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T50859, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 48859 - system wide software request: sbt
system wide software request: sbt
Status: RESOLVED FIXED
Product: Wikimedia Labs
Classification: Unclassified
tools (Other open bugs)
unspecified
All All
: Normal enhancement
: ---
Assigned To: Peter Bena
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-27 12:53 UTC by Martijn Hoekstra
Modified: 2013-06-05 10:31 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Martijn Hoekstra 2013-05-27 12:53:23 UTC
sbt (http://www.scala-sbt.org/) is a build tool for Java and Scala software similar to Maven, and it is the de-facto standard build tool for Scala. Though it could run in userspace, it is usual mode of installation is a system wide deployment. It is not available through the Debian or Ubuntu repositories, but is available as a .deb package. The now current version is found at http://scalasbt.artifactoryonline.com/scalasbt/sbt-native-packages/org/scala-sbt/sbt//0.12.3/sbt.deb and generally the most current version is linked from http://www.scala-sbt.org/release/docs/Getting-Started/Setup.html (it is a fairly fast moving target). I would like to have this software available on labs.

Because I hope but don't expect many people, if any people, other than me will be using this tool, and because there is no absolute need (merely a fairly large convenience) to have it installed system-wide (or even at all, though it is a great convenience to be able to use its dependency management which is an utter pain to do manually), i'm setting severity here to enhancement, and offer myself to assist with packaging and updating for as far that is desirable and I'm able to do so.
Comment 1 Peter Bena 2013-05-31 14:57:36 UTC
ok... so where do you actually want this to be installed?
Comment 2 Martijn Hoekstra 2013-05-31 16:25:41 UTC
I would like to be able to use it as a bot runner and compiler. I think that means exec nodes and tools-dev and tools-login? I'm not quite sure :S
Comment 3 Peter Bena 2013-06-04 15:05:24 UTC
hm... this package has some dependency problems, it relies on full java2-runtime which is very likely not necessary. We definitely don't want to have that on exec nodes, so, are you sure you need this on exec nodes as well? some repacking would be needed then...
Comment 4 Peter Bena 2013-06-05 08:47:42 UTC
I have installed this to -dev can you tell me if you need this package on exec nodes, or is -dev sufficient?
Comment 5 Martijn Hoekstra 2013-06-05 10:31:19 UTC
Hi Peter,

I suspect that it's not so much the java runtime, but the java SDK that would be problematic for the exec nodes. -dev only should suffice and teach me not to be lazy about building and publishing to a deployable state. Thank you for your effort. I'm working on getting sbt in a PPA so import of future versions will be easier. I've tested the current sbt setup on -dev and was able to build the trunk of my bot there and do a quicky testrun on -dev. I'm setting the status to fixed-resolved. Thanks!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links