You are not logged in.

#1 2018-12-27 11:18:10

xuanrui
Member
Registered: 2018-09-27
Posts: 10

Packaging software depending on really old version of LLVM

I have recently taken charge of the smlsharp package. It builds pretty well, but the only issue is that it depends on (a very small set of functionality provided by) LLVM 3.7.1. Now, I am not sure how to deal with this obsolete dependency:

1. package LLVM 3.7 into llvm37, like llvm35 and llvm39, and declare a conflict with llvm
2. package LLVM 3.7 into llvm37, like llvm33, installing into /opt instead of /usr, and don't declare a conflict with llvm
3. add the source of LLVM 3.7 into my source array and compile & install only what I need.

I'm thinking that is 2 probably the most sensible thing to do for my case. What is actually preferred then?

Offline

#2 2018-12-27 14:28:52

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 20,761
Website

Re: Packaging software depending on really old version of LLVM

Just my 2 cents: I agree 2 sounds best, but 3 seems like a reasonable alternative, 1 would almost certainly cause problems as users may want/need an up-to-date LLVM for other purposes.

Last edited by Trilby (2018-12-27 14:29:06)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

#3 2018-12-27 15:18:59

Slithery
Forum Moderator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 3,070

Re: Packaging software depending on really old version of LLVM

4. Get upstream to fix their project so that it builds with a modern compiler smile


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#4 2018-12-27 15:50:05

eschwartz
Trusted User/Bug Wrangler
Registered: 2014-08-08
Posts: 2,696

Re: Packaging software depending on really old version of LLVM

5) Build an llvm37 package that can be coinstalled into /usr/lib just like the [extra] packages llvm-libs and llvm6-libs can be coinstalled... and then get upstream to fix their stuff so it builds with a modern code generator.

Last edited by eschwartz (2018-12-27 15:53:35)


Managing AUR repos The Right Way -- aurpublish (now a standalone tool)

Offline

#5 2018-12-27 19:10:52

xuanrui
Member
Registered: 2018-09-27
Posts: 10

Re: Packaging software depending on really old version of LLVM

Slithery wrote:

4. Get upstream to fix their project so that it builds with a modern compiler smile

I am 120% sure that upstream won't fix - the package I'm maintaining is a research compiler (which happens to be actually useful), and upstream is likely not going to spend time on updating their dependencies, because they don't have time. So, we're kind of stuck with LLVM 3.7.1.

Offline

Board footer

Powered by FluxBB