public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps <cygwin-apps@cygwin.com>
Subject: [ITP] sbt 1.2.3-1
Date: Sat, 22 Sep 2018 21:02:00 -0000	[thread overview]
Message-ID: <7fd82def-37d7-f239-5601-f049706736b4@cornell.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

sbt is in Debian and Fedora:

    https://packages.debian.org/source/sid/sbt
    https://apps.fedoraproject.org/packages/sbt ,

although neither has the current version, and Debian's package is in
its unstable distro.

A more serious issue is that sbt requires java, which Cygwin doesn't
provide.  Cygwin users will have to install a JDK for Windows.  This
may or may not disqualify sbt as a Cygwin package.  The only similar
situation I know of is libusb0.

My cygport file is attached.

Package files:

http://sanibeltranquility.com/cygwin/noarch/release/sbt/sbt-1.2.3-1-src.tar.xz
http://sanibeltranquility.com/cygwin/noarch/release/sbt/sbt-1.2.3-1.tar.xz
http://sanibeltranquility.com/cygwin/noarch/release/sbt/sbt-1.2.3-1.hint

License: 2-Clause BSD

Ken

[-- Attachment #2: sbt.cygport --]
[-- Type: text/plain, Size: 1257 bytes --]

NAME="sbt"
VERSION=1.2.3
RELEASE=1
HOMEPAGE="https://github.com/sbt/sbt-launcher-package"

GIT_URI="https://github.com/sbt/sbt-launcher-package.git"
GIT_TAG="v${VERSION}"
inherit git

# The github repo doesn't seem to contain the jar files.  We'll get
# them from the Debian package.
SRC_URI+=" https://dl.bintray.com/sbt/debian/sbt-1.2.3.deb"

CATEGORY="Devel"
SUMMARY="An interactive build tool for Scala, Java, and more"
DESCRIPTION="sbt is an interactive build tool for Scala, Java, and more."
sbt_MESSAGE="In order to use sbt you will need to install a java development kit
for Windows, such as Oracle JDK 8 or OpenJDK 8."

DIFF_EXCLUDES="*.tar *.jar"

src_compile() {
    cd ${S}
    ar -x sbt-1.2.3.deb data.tar
    mkdir -p debian
    cd debian
    tar --wildcards -xf ../data.tar ./usr/share/sbt/bin/*.jar
}

src_install() {
    cd ${S}
    insinto /usr/share/sbt/conf
    doins src/universal/conf/*
    dodoc src/linux/usr/share/doc/sbt/* src/debian/changelog
    doman  src/linux/usr/share/man/man1/*
    exeinto /usr/share/sbt/bin
    doexe src/universal/bin/sbt src/universal/bin/sbt-launch-lib.bash
    insinto /usr/share/sbt/bin
    doins debian/usr/share/sbt/bin/*
    dodir /usr/bin
    dosym /usr/share/sbt/bin/sbt /usr/bin
}

ARCH=noarch

                 reply	other threads:[~2018-09-22 21:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7fd82def-37d7-f239-5601-f049706736b4@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).