Re: Removal of libllvm4.0 from disco/universe
For what it's worth, I just forward-ported 3.9 from xenial to disco because the alternative was reformatting a bazillion lines of source code. It wasn't too hard, just had to do 'apt source clang-format' on an ubuntu 18.04 box, transfer the source to a 19.04 box, install gcc 7 and make three little changes to the package, to wit: http://kegel.com/linux/llvm-ubu1904.patch There's probably a PPA somewhere with older versions of clang-format, but if there isn't, I could create one. - Dan -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Removal of libllvm4.0 from disco/universe
Hi Simon, On Sun, May 12, 2019 at 02:02:41PM +0200, Simon Spannagel wrote: > I was wondering why libllvm4.0 (or, more specifically for me, > clang-format-4) was removed from the 19.04/disco/universe repository > while an even older version (3.8) is still available. > > What were the reasons for removing it? The reason given was: "(From Debian) ROM; Would like to limit the number of versions; Debian bug #893401". This can be viewed at: https://launchpad.net/ubuntu/+source/llvm-toolchain-4.0/+publishinghistory and the Debian bug referenced is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893401 >Is there any chance this could be > re-added? This is unlikely. Disco is now released, and changes to stable releases are restricted to meet user expectations. See https://wiki.ubuntu.com/StableReleaseUpdates. Additionally, maintaining extra versions of things requires extra work, and so we generally don't maintain multiple versions of things where possible. Finally, maintenance work for this package is done by volunteers, and it's up to the volunteers what they want to spend their efforts maintaining. Hope that helps, Robie signature.asc Description: PGP signature -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: SV: compatibility issue in environment-modules version 4.1.1-1
On 2019-05-13 09:22, Gösta Ljungdahl wrote: -Ursprungligt meddelande- Från: Gunnar Hjalmarsson [mailto:gunna...@ubuntu.com] Ämne: Re: compatibility issue in environment-modules version 4.1.1-1 When reading that I think: If variables are defined at initialization, which are needed later on, why not simply turn them from pure shell variables to environment variables by export'ing them? That would be a change of the environment-modules code which ought to be doable. I'm not sure I understand what you mean. The environment variables and shell functions that the initialization defines are exported with the intent of making them available to the environment. Dash when later called upon accepts the exported variables but washes the exported shell functions out as I understand it at this point. Ok, if the program relies on exported functions, I understand better. https://stackoverflow.com/questions/29239806/how-to-export-a-function-in-bourne-shell -- Gunnar Hjalmarsson https://launchpad.net/~gunnarhj -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
