These are chat archives for sbt/sbt-native-packager

30th
Jan 2016
Dmytro Aleksandrov
@alkersan
Jan 30 2016 09:27
@muuki88 Unfortunately deb repositorys are in commercial Artifactory only. But as far as I know - lots of teams (including mine) have it. I've checked another product - http://www.aptly.info/doc/api/files/, it's free, simple to use and also supports deployment of packages via HTTP API.
Nepomuk Seiler
@muuki88
Jan 30 2016 10:21
Then I would recommend a new sbt project. Are you interested and have a bit of time to maintain it? We could add it to the related plugins and to the docs
Dmytro Aleksandrov
@alkersan
Jan 30 2016 10:27
@muuki88 a separate plugin just to do one http request? You have restrictions on dealing with commercial products?
@muuki88 and yes, I have interest and time to maintain it. I'd gladly made a contribution
Nepomuk Seiler
@muuki88
Jan 30 2016 10:49
We don't have any restrictions on commercial products
I'm only not sure if it belongs in native-packager as it provides ways of packaging. The deploy plugins just leverage the sbt internals
I'm interested in what the other maintainers have to say. Widen the scope or not @jsuereth @metasim @fiadliel
Nepomuk Seiler
@muuki88
Jan 30 2016 10:55
Thinking more about it, for docker we have this feature ( but only because in docker it's built into the daemon )
Dmytro Aleksandrov
@alkersan
Jan 30 2016 11:02
@muuki88 IMHO in current state DebianDeployPlugin is pretty much useless I think. I didn't met anybody who wanted to keep linux packages in mavencentral/nexus/etc..
Nepomuk Seiler
@muuki88
Jan 30 2016 11:04
Fair point
( I didn't either :smile: )
IIRC nexus was able to build rpm repos out of maven repos. However I must admit I never tried
As you already wrote the code. Let's open a PR a discuss this on the PR, so als these valids points are listed where they belong. I'm really open for all options
Dmytro Aleksandrov
@alkersan
Jan 30 2016 11:08
@muuki88 almost there
Nepomuk Seiler
@muuki88
Jan 30 2016 11:24
Nice. I will take a look this evening
Simeon H.K. Fitch
@metasim
Jan 30 2016 14:54
@muuki88 @alkersan: I reviewed the discussion, and if I understand correctly, the proposed plugin is relating to the publishing phase of packaging, not the formatting of the packaging. If that's correct, I'd argue it's not within the scope of the project. As an analogy, I'd say the same thing about publishing to the Apple App Store from the JDKPackagerPlugin MacOS X support: not in scope.
That said, I'd argue strongly for a set of conventions and base plugins (like sbt-web) to support package publishing of all formats.
Maybe sbt-bintray could be a starting point.
Dmytro Aleksandrov
@alkersan
Jan 30 2016 15:08
@metasim I see your point - the division of module responsibilities
@muuki88 I've made PR. In case if you decide that packager is not the right place - I'll probably start separate plugin with dependency on packager.
Nepomuk Seiler
@muuki88
Jan 30 2016 15:18
Okay cool. If we decide not to merge, we surely help promoting :)