Code: Select all
Alpine clang version 5.0.1 (tags/RELEASE_501/final) (based on LLVM 5.0.1)
Now I see. Alpine, who do not write clang, decided they should put their distro name in the string, which is downright absurd. Tough to fix in pinxi, because it expects, quite reasonably that program version strings will be what they are.
Hmm, I know, I'll add in one more test, if the value received is version, increment the snip by 1.
That may work, since most cases I've seen now that are wrong are the result of people adding in a word before the actual application name, which almost never happens, but I've seen enough cases now where I think that fix is the best I'll try, and I think it will fix that class of errors.
Thanks for these examples of yet more fringe cases, these have been enormously helpful, much appreciated.
Will fix this in 0454, that's a pretty easy regex check. It will work in most cases where this type of string add was made, and version was teh found term, and I think I'll draw the line there, after that, it's really outside of the scope of pinxi in my opinion.
Actually, now I'm confused, pinxi is already snipping out the 4th item. hmm. I just realized, this was a fix I did to try to fix the wrong clang version line, so I have to revert that, and then add in the snip increment check.
Code: Select all
# freebsd
clang version 3.7.1 (tags/RELEASE_371/final)
Target: x86_64-unknown-freebsd10.3
Thread model: posix
#another freebsd
clang version 3.7.1 (tags/RELEASE_371/final)
Target: x86_64-unknown-freebsd10.3
Thread model: posix
# linux
clang version 5.0.1 (tags/RELEASE_501/final)
Target: x86_64-unknown-linux-gnu
Thread model: posix
InstalledDir: /sbin
MY basic inclination in such cases is to file a bug report against alpine clang, and tell them to get rid of their name in that position, but pinxi will try to handle it since there's no telling when people will do things like this.
The init stuff I'd really like to solve however, I'm trying to get some data on that to see what's up. I think it's fixable.