An update, things seem to be running mostly smoothly again now. If your package is still not working, please file an issue (and try to diagnose it yourself using the virtual machine).
On Sunday, March 1, 2015 at 11:17:15 AM UTC-5, Iain Dunning wrote: > > Hi James and Seth, > > Dependency networks definitely interest me (see my blog post on the topic: > http://iaindunning.com/2014/pkg-deps.html) > > The code is all there, so my plan is to hook it up to the website next so > its automatically generated nightly. > > As for function call analysis, definitely possible (using JuliaParser.jl?) > although too much of a project for me. I'd be happy to help someone with it > though. > > Cheers, > Iain > > > On Sunday, March 1, 2015 at 10:56:55 AM UTC-5, Seth wrote: >> >> This is a really fantastic idea, and one that I'd love to help with. The >> lack of information about which packages rely on which others means 1) >> we've made breaking changes that were totally unanticipated, and 2) we're >> hesitant to make changes because we don't know who to notify. >> >> Seth. >> >> On Saturday, February 28, 2015 at 7:57:56 PM UTC-8, James Fairbanks wrote: >>> >>> >>> Also I am interested in the dependency network, which we can get out of >>> the REQUIRE files. Which packages are providing functionality that many >>> others depend on in an indirect way? These would be important packages to >>> keep well maintained because if they fail many other packages will fail. >>> What are the clusters of packages? >>> >>> James Fairbanks >> >>
