Provide separate packages for each major version (clang-3.0, etc)
Bug #1133401 reported by
André Stein
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| clang (Debian) |
Fix Released
|
Unknown
|
|||
| clang (Ubuntu) |
Incomplete
|
Wishlist
|
Unassigned | ||
Bug Description
GCC/G++ is provided with several supported version like g++-4.6 and g++-4.7. The same procedure should be adopted for clang. So a clang-3.1 package should be provided for projects which have build dependencies on the older version.
| summary: |
- Also provide clang-3.1 as package + Provide separate packages for each major version (clang-3.0, etc) |
| Changed in clang (Debian): | |
| status: | Unknown → New |
Revision history for this message
| Matthias Klose (doko) wrote | #1 |
| Changed in clang (Ubuntu): | |
| importance: | Undecided → Wishlist |
| status: | New → Incomplete |
| Changed in clang (Debian): | |
| status: | New → Fix Released |
To post a comment you must log in.
no, it should not, "because GCC does it". Older GCC versions are there for front ends not available in newer versions, e.g Dv1, Dv2. Ubuntu is not a software museum, so please give examples why you would need these old versions, and which software cannot be built with newer versions.