Bug 601573
Summary: | Consider to package clang seperately | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Chen Lei <supercyper1> |
Component: | llvm | Assignee: | Michel Lind <michel> |
Status: | CLOSED DEFERRED | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | bos, dmalcolm, jgarzik, michel |
Target Milestone: | --- | Keywords: | EasyFix |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-10 16:19:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Chen Lei
2010-06-08 08:39:54 UTC
Clang is designed to be built as part of the LLVM project: http://clang.llvm.org/get_started.html so I don't think it actually counts as a different project here. They are released simultaneously too. Let me know if you think this explanation suffices, in which case I can close the bug, otherwise, it might be nice to get a clarification from the Packaging Committee. (In reply to comment #1) > Clang is designed to be built as part of the LLVM project: > http://clang.llvm.org/get_started.html > so I don't think it actually counts as a different project here. They are > released simultaneously too. > Let me know if you think this explanation suffices, in which case I can close > the bug, otherwise, it might be nice to get a clarification from the Packaging > Committee. I think it'll be much better to package it seperately, other distributions such as debian, gentoo package llvm and clang seperatley. In fedora, at least font guideline don't permit bundling several tarball in one srpm. http://fedoraproject.org/wiki/Packaging:FontsPolicy Take xulrunner for a example, several months ago fedora package them in one srpm along with xulrunner-python. Now, we package them seperately because upstream release them in two seperate tarballs. qt/qt-qt-assistant-adp and libktorrent/ktorrent is the same case. I appreciate the comparison to other cases, but again, in this case these are two tightly coupled projects where it would not, as yet, make much sense to package them separately. Looking at the Gentoo example: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-devel/clang/clang-2.7.ebuild?revision=1.1&view=markup They actually downloaded an entire copy of LLVM, build it, and clang, but then only package the clang bits. There's this upstream bug report, that's oddly marked as CLOSED despite clang not really being easily buildable out-of-tree, http://llvm.org/bugs/show_bug.cgi?id=4840 Once clang has clear instructions for building out-of-tree then I'll certainly create a separate package for it, and make whatever (reasonable) modifications to our LLVM package needed to get it to compile. However, at the moment it does not seem like the most productive use of time. PS A lot of non-font packages do come with multiple tarballs. See for example pidgin. |