Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
Justin Kaeser
@jastice
yo.
hacking infrastructure
Jorge
@jvican
yo!
What's this ? :D
Justin Kaeser
@jastice
infrastructure for this https://github.com/libling/sbt-hackling
Jorge
@jvican
that's great man
what's the difference with the source dependencies support built-in into sbt?
Justin Kaeser
@jastice
this copies source deps into the target or directly into repo
and the idea is to have more usable infrastructure around it
ability to resolve from different repos, resolve/update by tags or branches, dependency locking, transitive dource dependencies,e tc
Justin Kaeser
@jastice
sheesh, getting travis publishing on bintray right is ~_~
another reason i'm doing this
Justin Kaeser
@jastice
Dale Wijnand
@dwijnand
Nice one mate
Justin Kaeser
@jastice
:D
Shane Delmore
@ShaneDelmore
@jastice Neat project. Do you happen to have a list of libling's (is that the right term?) available or is it still too early for that?
Justin Kaeser
@jastice
um, I just started building this yesterday
but I've already made a template! https://github.com/libling/libling.g8
if you were to pack up some functions in a libling and upload it, that would be great to try it out
Shane Delmore
@ShaneDelmore
Might not have time to mess around with it for a few days but sounds like fun. I'll let you know if I learn anything interesting.
Justin Kaeser
@jastice
coolies
I should have the basic functionality down by then
Justin Kaeser
@jastice
documentation and transitive resolving and lockfiles and stuff: https://github.com/libling/libling-with-transitive-dependencies
Raam Rosh-Hai
@raam86

Really cool concept @jastice, I've created my first libling and it's actually quite straight forward, It was quite magical to do liblingInstall and to be able to import stuff usign cmd+enter

Here's the repo
https://github.com/raam86/akka-streams-htrace-libling/blob/master/README.md

Justin Kaeser
@jastice
:tada: :tada:
sweet!
Raam Rosh-Hai
@raam86
A really nice thing I didn't think about was that resolving the deps was almost instant, much faster the using ivy!
Justin Kaeser
@jastice
well at least as long as the repos are small!
also they are cached
I guess that can make it quite fast
now some sort of index would be neat
Raam Rosh-Hai
@raam86
Since there's no publishing step, how would you suggest to approach it?
Justin Kaeser
@jastice
not sure. PR to a repo?
Raam Rosh-Hai
@raam86
so it's a github integration with a webhook to register the libling in the libling index
Justin Kaeser
@jastice
possibly. there would only need to be some place where it can send a few parameters and then something pushes to a repo after verifying it's a libling
Raam Rosh-Hai
@raam86
The "event collector" is quite trivial to implement I am just not sure where we can hook into the current libling lifecycle
Justin Kaeser
@jastice
it can be a separate task
Justin Kaeser
@jastice
ah, there should also be a task that deploys the libling directly to github
Justin Kaeser
@jastice
what problems could it cause to rewrite the packages of a libling when importing it? (ignoring reflection)
Dale Wijnand
@dwijnand
Things binding to its public API. For example if it has a method that returns foo.Foo things aren't going to compile if you rewrite it to bar.internal.foo.Foo
Justin Kaeser
@jastice
are there reasonable workarounds for this?
Dale Wijnand
@dwijnand
Not to my knowledge. "Don't use your own types in your API" is the way this is avoided in other languages, but I personally don't consider that reasonable.
Justin Kaeser
@jastice
I guess as long as the scope is "simple utility functions" it's an acceptable option to resolve conflicts
Justin Kaeser
@jastice

The official contribution policy is now:

This is an experimental platform. You are encouraged to submit changes. Almost anything will be accepted without much fuss.

cheers!