Red Hat Bugzilla – Bug 601573
Consider to package clang seperately
Last modified: 2010-06-10 12:19:05 EDT
Description of problem:
According to fedora package guideline, different project should be packaged seperately.
It'll be better to package clang seperately, thank you!
Clang is designed to be built as part of the LLVM project:
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:
> 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
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.
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:
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,
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.