This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-06-28
Channels
- # aleph (2)
- # beginners (25)
- # boot (12)
- # cider (73)
- # cljs-dev (3)
- # clojure (37)
- # clojure-dev (93)
- # clojure-germany (1)
- # clojure-italy (24)
- # clojure-nl (21)
- # clojure-russia (26)
- # clojure-spec (37)
- # clojure-uk (80)
- # clojure-za (1)
- # clojurescript (47)
- # cursive (4)
- # data-science (17)
- # datomic (69)
- # emacs (19)
- # events (7)
- # fulcro (41)
- # hoplon (14)
- # leiningen (2)
- # nrepl (4)
- # off-topic (253)
- # om (11)
- # portkey (2)
- # re-frame (11)
- # reagent (24)
- # ring-swagger (1)
- # rum (5)
- # schema (1)
- # shadow-cljs (106)
- # specter (2)
- # tools-deps (91)
I'd like to use :local/root
to tie up my dependent projects in the monolith repo, but I have an issue with one of the dependencies. It has one Java source file. Can you recommend, how to handle this?
Well one solution is to move it into its own project and make an artifact
@alexmiller ^ is this an intentional behaviour?
there’s a ticket, send me a patch :)
I just haven’t gotten to it yet
actually, maybe nobody made a ticket so feel free to make one in https://dev.clojure.org/jira/browse/TDEPS
yeah, the "problem" I reported a few days back was because the alias wasn't properly configured; a simple name check would caught this
happy to fix
It's bitten me a couple of times so I'll vote that ticket 🙂 but it hasn't bitten me hard/often enough for me to summon up the energy to create such a ticket...
today in #tools-deps: extremely extreme bugs! do they bite hard and often enough for a ticket? do they come from the Australian mainland? only jira can tell!
if no else patches I’ll get to it when I next work on TDEPS
Yes, thank you, Alex!
Hopefully it can be ported to POSIX shell without any bash, that would be a nice improvement 🙂
root@abel:~# python
-ash: python: not found
root@abel:~# node
-ash: node: not found
root@abel:~#
Installing Python/Node is trivial. Point is you get a script that is portable to any OS.
Also that means testing the script under several implementations (busybox, dash and bash at least). Not worth it.
@dottedmag that's unfortunate. Although I did stumble onto https://github.com/Ventto/libshlist recently.
I personally am ready to remove bash for all but clojure on my system. I use dash & fish primarily.
because I wrote it and I don’t like Python or JS :)
@alexmiller So 💎 ruby?
for whatever reason, I just don’t get Ruby.
Oh really? Oh I was not expecting that response. I suppose you're not from the ruby shop that's associated with Clojure 😛. You strike me as a perl guy? 😉
I feel this is the exactly the kind of conversations that cause Codes of Conduct written which precludes snarky remarks and personal attacks.
I have used all of these languages profesionally
@dominicm The point of clojure
is to just work. Anywhere. Without installing anything.
and I respect people that like and use all of them
@dottedmag just to be clear, I actually hold no contempt for any of these languages. I feel like I have a fairly good grasp of where each one is pretty good. I agree. I don't actually think ruby is suited here.
bash
is far and away the lowest common denominator on Unix-ish systems, with the possible exception of sh
, which on many distros just links to bash.
it absolutely sucks, but if your goal is maximum multi-year portability, there's no other viable alternative
I’ve grown to almost like it
having done the windows port to powershell, that wasn’t bad either
@alexmiller Oh, there is PowerShell one? In the same repo?
it’s on a branch I think
if I pushed it
there's a team at work that has >100k written in bash, with strict coding guidelines and practices it can work. You can grow to like many things if you immerse yourself in their idiosyncrasies :)
it’s not done yet
it’s kind of like if you took bash and applied sane engineering to it
heck, powershell does autocomplete of function arguments on the command line. It's kinda impressive
@kenny the goal is not to install anything except what is required to bootstrap clojure
stop trying to oppress me man
the water’s fine, come on in
@hagmonk (and any others) I just pushed up 857bbc85c33b23b5f8e51d68eb724776564d9c16
to juxt/pack.alpha which adds skinny jar support, it spits it out in multiple forms based on the parameters. Any feedback welcome!
I don't really have a concrete use case myself yet, so I'm guessing at things a little.
I had to do a little bump, having :
in filenames doesn't go well with classpaths, 800afc066907e31fe90ce4df4f519e6224116867
is the latest commit
It's in alpha-alpha, as it's not in master yet, I'll be rebasing at some point, but I won't force push over those commits.
on the off-chance that you're not trolling, that would be way too much friction
So quick story time about the clojure installer being written in bash: the other day I was mucking with Homebridge on a raspberry pi, and needed to do some interrogation of a web API. In five minutes I had a Clojure REPL up with rebel readline, it was great. Had the installer required ruby, python, perl, etc, I would have had to dive into the Pi's package management and pull a ton of unrelated crap down, just to get a REPL. Had clojure needed a version of nodejs that was in any way incompatible with homebridge, I would have immediately faced the problem of juggling multiple npm versions. An example of the leverage you get from picking the unsexy, boring, lowest common denominator for bootstrapping tools