LLVM PPA: Script source availability

[Sylvestre Ledru]

Le 21/02/2022 à 15:18, Whisperity a écrit :
> In addition: I am specifically looking for the people/community
> maintaining the "nightly" APT.LLVM.ORG and **not** the official
> release Debian package repository.
> I might be sending mails to the wrong place?

This is the correct place but I am almost the only one doing the maintenance of both.
apt.llvm.org is the nightly stuff of what I am uploading in Debian & ubuntu.
They are really the same.

> I was working off of this information:
> 
>> $ apt-cache show clang-12 | grep 'Version\|Maintainer'
>> Version: 1:12.0.1~++20211216045758+fed41342a82f-1~exp1~20211216170241.12
>> Maintainer: LLVM Packaging Team <pkg-llvm-team at lists.alioth.debian.org>
> 
> On Mon, Feb 21, 2022 at 3:14 PM Whisperity <whisperity at gmail.com> wrote:
>>
>> Dear Sylvestre,
>>
>> I understand, but these are almost ten-year-old threads at the moment.

Sorry but what do you think changed in 10 years in the Debian and Ubuntu packaging world ? ;)
(not trolling, I am just saying that most of the fundamentals are still the same)


>> Are we sure the state of the world did not change at all since, and
>> the arguments there (already contested by others) are still valid?
>> 'llvm-default' or 'llvm-defaults' does not even turn up any packages
>> at this point (on Ubuntu 18.04 or Debian 10).
I don't remember a time for which llvm-defaults installed anything.

llvm-defaults provides the clang, lldb, lld, etc symlink to point a specific version.
Example:
https://packages.debian.org/unstable/clang
https://packages.debian.org/unstable/lld

If you want to use a specific version of clang, run
CC=clang-13 ./configure
(or the equivalent).

What is wrong this that solution?

Now, if you have something ready for a MR, feel free to submit it. I will be happy to have a look to it.

>> For example, someone already mentioned Java there, and indeed (taken
>> from an Ubuntu 18.04.6 LTS system):
>>
>>> ╰─ update-alternatives --query java
>>> Name: java
>>> Link: /usr/bin/java
>>> Slaves:
>>>   java.1.gz /usr/share/man/man1/java.1.gz
>>> Status: auto
>>> Best: /usr/lib/jvm/java-11-openjdk-amd64/bin/java
>>> Value: /usr/lib/jvm/java-11-openjdk-amd64/bin/java
>>>
>>> Alternative: /usr/lib/jvm/java-11-openjdk-amd64/bin/java
>>> Priority: 1111
>>> Slaves:
>>>   java.1.gz /usr/lib/jvm/java-11-openjdk-amd64/man/man1/java.1.gz
>>>
>>> Alternative: /usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java
>>> Priority: 1081
>>> Slaves:
>>>   java.1.gz /usr/lib/jvm/java-8-openjdk-amd64/jre/man/man1/java.1.gz
>>
>> There were a lot of changes from Java 8 to 11 on the command-line
>> interface which makes the two incompatible. (Although most of those
>> are not everyday-used flags.)
Yeah, Matthias (who particpated to the discussions on launchpad) and I (at some point)
have been maintaining openjdk packages too.

It also uses a similar approach to llvm-defaults:
https://packages.debian.org/buster/default-jre (and others)


Cheers,
Sylvestre