cljsjs

juhoteperi 2016-05-19T17:59:02.000589Z

@martinklepsch: huh, Clojars doesn't accept emojine package because it is too large

juhoteperi 2016-05-19T18:00:00.000590Z

Clojars max Jar size is 20MB

juhoteperi 2016-05-19T18:01:28.000591Z

Maybe the font files are most important? Presumable they are used by css

juhoteperi 2016-05-19T18:02:53.000592Z

Or not. JS seems to use images.

martinklepsch 2016-05-19T18:28:25.000593Z

I'll try to cut some stuff, fonts are least important as far as I can tell, not sure if that'll be enough though

martinklepsch 2016-05-19T18:28:30.000594Z

@juhoteperi: ^

juhoteperi 2016-05-19T18:29:14.000595Z

I would guess the pngs take the most space

martinklepsch 2016-05-19T18:47:10.000597Z

weirdly that's not the case and one of the fonts takes 35mb

martinklepsch 2016-05-19T18:47:41.000598Z

after removing the font it's at 21, just removed the large pngs as well now @juhoteperi

flyboarder 2016-05-19T20:24:13.000600Z

@juhoteperi: what is the proper way of dealing with forks of libraries?

juhoteperi 2016-05-19T20:26:20.000601Z

@flyboarder: There is no proper way currently

flyboarder 2016-05-19T20:27:36.000602Z

ok

juhoteperi 2016-05-19T20:28:07.000603Z

I think best way would be to package them outside of cljsjs, in your own repo

flyboarder 2016-05-19T20:29:54.000604Z

yeah I am currently maintaining a local repo with branches to different developers, but that means installing the package locally each time i switch

juhoteperi 2016-05-19T20:30:39.000605Z

If the original version is abandoned and fork is the de-facto replacement, it would be okay to include in it Cljsjs. But in other cases I would prefer to keep these out of Cljsjs for simplicity.

juhoteperi 2016-05-19T20:31:26.000606Z

what do you mean installing locally each time you switch?

juhoteperi 2016-05-19T20:31:37.000607Z

I would recommend changing group name, package name or version and just pushing it to clojars

flyboarder 2016-05-19T20:33:29.000609Z

yeah i was just wondering if there was a better way than managing another repo

flyboarder 2016-05-19T20:35:15.000610Z

but that seems like the easiest way to go

juhoteperi 2016-05-19T20:36:42.000611Z

Should be as simple as maintaining any Clj(s) library

flyboarder 2016-05-19T20:45:08.000612Z

right but i dont really want to manage 40 libraries under my group name because i have 20 js libraries wich we have our own forks, and then 20 cljsjs libraries to get cljsjs jazz

juhoteperi 2016-05-19T20:45:44.000615Z

huh, that is many forks

flyboarder 2016-05-19T20:45:59.000616Z

well a few forks across many projects adds up

flyboarder 2016-05-19T20:46:37.000618Z

if we have 6 projects and each of them fork maybe 3 dep projects

flyboarder 2016-05-19T20:46:57.000619Z

i was mostly wondering if there was something built-in

flyboarder 2016-05-19T20:47:15.000620Z

but if not, ill just write more boot tasks to deal with things XD

juhoteperi 2016-05-19T20:47:34.000621Z

you could copy the CI scripts from cljsjs and setup your own CI to ease the pain

juhoteperi 2016-05-19T20:48:02.000622Z

or try to make the forks unncessary, send changes to upstream, workaround locally, replace libraries etc.

juhoteperi 2016-05-19T20:48:56.000623Z

I have done around 10 Cljs projects and only libraries I have used are React, Leaflet (and react-leaflet) and Pikaday (now replaced with Reagent component)