https://bugzilla.redhat.com/show_bug.cgi?id=1109390 --- Comment #5 from Christopher Meng <i@xxxxxxxx> --- (In reply to Milan Bouchet-Valat from comment #3) > (In reply to Christopher Meng from comment #1) > > Per your strategy, will there come llvm3.4, llvm3.5 in the future? Because > > LLVM API is never stable. > Well, it really depends on how Fedora's and Julia's schedules interact in > the future. It depends on Julia itself, actually. > But OTOH when backporting a new LLVM version to a published Fedora > release, it's likely that Julia will break as there will likely be some lag > between LLVM's and Julia's releases. I don't think you need to update julia for each Fedora release, we need to keep something stable. > With an unstable API like LLVM's, > versioned parallel-installable packages are kind of inevitable. Still not a good reason. If something can't be considered stable, you'd better package it in copr first. > (In reply to Jens Petersen from comment #2) > > Does Julia upstream have any plans to move to llvm-3.4 btw? > Yes, the next version will use LLVM 3.5. (Support for 3.4 is almost present > already, but there are a few bugs and it has not been tested thoroughly > enough that the developers feel confident to use it now.) Oh, so llvm3.5 will appear in review queue again? What about 3.6, 3.7, 3.8 etc.? -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review