On 4/27/24 05:57, Neal Gompa wrote:
On Sat, Apr 27, 2024 at 5:53 AM Tom Stellard <tstellar@xxxxxxxxxx> wrote:
On 4/26/24 21:58, Neal Gompa wrote:
On Fri, Apr 26, 2024 at 9:35 PM Tom Stellard <tstellar@xxxxxxxxxx> wrote:
Hi,
After each Fedora release we do a retrospective with the LLVM package maintainers
and talk about how we can improve the LLVM packages[1] in Fedora. We've come up
with some ideas for Fedora 41 that we'd like to share to raise awareness and
get feedback. Right now these are just ideas, and we plan to write up a formal
change proposal once we have decided which of these we are going to implement:
Here's some feedback below for each of these ideas.
* Spec file merge. We plan to merge the clang, compiler-rt, and libomp packages
in with llvm and have them be sub-packages of the llvm package. This will allow
us to use the build configuration recommended by upstream and also make it possible
to optimize the packages using Profile-Guided Optimizations (PGO).
Are these actually released together or are they separately developed
and lifecycled? If it's the latter, this would make things much more
complex down the road because you'll have to deal with a lot of the
weirdness that Nodejs deals with by having to subpackage with
different versions and trying to keep the release values coherent so
that every NVR of every subpackage is correctly unique. It's not worth
it in that case.
These projects are all part of the same git repository upstream.
That doesn't actually matter from the perspective of Fedora. What
matters is if these components are versioned, released, and supported
together.
They are, this is main reason why they were put in the monorepo together.
- Tom
To put it in developer terms: a monorepo is a Git repo of multiple
projects that have independent release lifecycles. The only reason
they are there is because the developer wants them there. That's in
contrast to say the Linux kernel, which has a huge uniform repository
of components developed by separate people that are released together
and considered a single unit from a release lifecycle perspective and
share versioning.
--
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
