Package: llvm-defaults, llvm-toolchain-3.3, llvm-toolchain-snapshot upstream's marketing material doesn't belong into the package descriptions. The llvm package descriotions do have a much more neutral way of describing ths packages.
> Clang project is a C, C++, Objective C and Objective C++ front-end > for the LLVM compiler. Some of its goals include the following: If these are just goals, they maybe don't belong into the package description. > End-User Features: > . > * Fast compiles and low memory use So do other compilers. It very much depends which optimization options are used. > * Expressive diagnostics (examples) Which examples? > * GCC compatibility well, ok. but which compatibility? certainly not the license > Utility and Applications: > . > * Modular library based architecture > * Support diverse clients (refactoring, static analysis, code > generation, etc) how does this belong into the clang binary package? > * Allow tight integration with IDEs > * Use the LLVM 'BSD' License well, Debian has the copyright file for this. > Internal Design and Implementation: > . > * A real-world, production quality compiler so we have to document all other compilers as toy compilers? > * A simple and hackable code base yes, need to rewrite every reverse dependeny for each llvm/clang release. > * A single unified parser for C, Objective C, C++, and Objective C++ > * Conformance with C/C++/ObjC and their variants conformance to what? standards? Which variants? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
