On Sun, Jul 16, 2023 at 7:30 AM Kevin Kofler via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Miao, Jun wrote: > > Hi Guys, > > First of all, we are not all guys. (I happen to be one though.) I would advise not to get too picky about this. The term "guys" isn't necessarily gender-specific. In its plural form, it has basically replaced "folks" in many English dialects, and holds the same non-gendered meaning. The antonyms, "guy" and "gal" have largely fallen out of favor in English, with the latter being quite rare, and the former's plural form evolving into a non-gendered usage, similar to "dude(s.)" and "dudes(pl.)" being used in non-gendered ways. While I think it's a good idea to use gender-neutral language when gendered language isn't needed, this one actually is pretty gender-neutral already, at least in the way many people use it. So, I recommend not reading too much into casual greetings like this. Getting too picky runs the risk of polarizing people and making it harder to make changes for the better where it matters. Assuming good intentions, it seems like the author intended this in the common, modern, non-gendered plural form to me. > > > AFAIK, the Yocto Project is an open source collaboration project that > > provides tools, templates, and methods to help developers create custom > > Linux-based systems for embedded devices. > > > > My confusion is that: > > > > 1. what`s the tool to make our Fedora Linux 38 released like Yocto? > > There is more than one tool in use. The main build tool is Koji, but it > depends on other underlying tools such as Mock, DNF, RPM, etc. Also keep in > mind that in Fedora, all binaries are natively compiled, not cross-compiled > as in Yocto. I.e., the rpmbuild process needs to run on a (real or emulated) > CPU of the architecture for which you want to build the package. RPMs do not > typically support cross-compilation. When I saw the original post, I was interested to see what responses it would trigger. I must admit that this one is a bit disappointing. While I've been building RPMs for Fedora for awhile now, one of the things that has eluded me is that the Fedora OS composes seem to be very opaque to me. I know enough to understand that Koji tags rpm builds from individual buildroots, but from there, the process to build the repos and the installation media, or how the buildroots are created in the first place for Koji, or any other weirdness involved in the construction of the OS as a whole from the individual RPM builds, all of that seems opaque to me. I think it'd be great if there was an up-to-date and detailed step-by-step guide for how to build a Fedora release. Such documentation should be detailed enough that one could stand up their own fork of the Fedora OS... not because we want to encourage that... but because that's the level of detail that I think is needed to allow volunteers to step in and get involved, as the current folks move on, due to retirement, death, boredom, or whatever. If such documentation already exists, I don't know where it could be found. Do you know of any such detailed documentation, step-by-step instructions, or maybe slides/presentations on the compose process or overall Fedora OS build systems? > > > 2. And Centos ? > > The only CentOS that is left is CentOS Stream, which (as far as I know) also > uses Koji. > > The CentOS successors such as Rocky Linux and AlmaLinux are free to either > also use Koji or use their own tools, or a combination. E.g., Rocky Linux > has developed Peridot. > > > 3. And Ubuntu ? > > Ubuntu has its own completely different tooling built around Debian's > tooling and Canonical's Launchpad platform. > > Kevin Kofler > _______________________________________________ > 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 _______________________________________________ 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
