Search results

* [[BaseRuntime/Fedora_26_MVP|Base Runtime Fedora 26 MVP]] ...ress.com/2017/05/30/sausage-factory-an-introduction-to-building-modules-in-fedora/ Building modules in the Module Build Service]

== Base Runtime Fedora 26 MVP == ...document is to describe the Base Runtime minimum viable product (MVP) for Fedora 26, defining the role & structure of the Base Runtime module as well as its

...Platform is an evolution of the Base Runtime module concept introduced in Fedora 26 Boltron, splitting the minimal system further into independent modules a * Targeted release: [[Releases/27 | Fedora 27 ]]

# Fedora Extras repository is enabled by default from Fedora Core 4 onwards. # Pup in Fedora Core 5 can update both Core and Extras repositories

{{DISPLAYTITLE:Fedora Packaging Guidelines for Modules}} {{#fedoradocs: https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modules/}}

...d" to be able to help out remotely. The best way to do this is to sit in #fedora-admin and listen for updates and other such messages to come about. * Fedora SCM

...d to have this defined, but that is not the case for building packages for Fedora and for CentOS and EL versions newer than v5. Leave it out of your RPM spec Fedora (still, as of even version 25) lists acceptable package groups in /usr/shar

In Fedora, there is a lot of applications and daemons which require customized SELinu ...x-policy%5Bgithub.com/fedora-selinux/selinux-policy and https://github.com/fedora-selinux/selinux-policy-contrib.

...oles in the library long after it is fixed upstream. Mono applications in Fedora cannot include upstream DLLs (even if they are compiled from source). This

Fedora Core 5 introduced a new SELinux feature: loadable policy modules. ...integrate the policy with the monolithic base policy, as was the case for Fedora Core 4 and earlier releases.

...focuses on creation of tools for building the OS 'firmware' images from a Fedora OLPC yum repository. All the Fedora OLPC projects are maintained using the Mercurial source control tool. With

* Targeted release: [https://docs.fedoraproject.org/en-US/releases/f39/ Fedora Linux 39] * Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/986 #986]

In Fedora, there is a lot of applications and daemons which require customized SELinu ...inux/selinux-policy/tree/rawhide/policy/modules/contrib https://github.com/fedora-selinux/selinux-policy].

...ments the guidelines and conventions for packaging [[Haskell]] projects in Fedora. Standardizing the packaging helps to lower the maintenance burden across Fedora's Haskell packages.

...oles in the library long after it is fixed upstream. Mono applications in Fedora cannot include upstream DLLs (even if they are compiled from source). This

...solving SELinux issues at the packaging level. This page is only valid for Fedora Core 5 and newer. * http://www.redhat.com/archives/fedora-selinux-list/2006-April/msg00094.html

...better and beyond what it is today. The project has grown long ways since fedora.us days but no need to stop here. There is still enough stuff to do and mor I first got involved with the fedora project at fedora.us. I was not that active back then and it took me a while to get as active

...ments the guidelines and conventions for packaging [[Haskell]] projects in Fedora. Standardizing the packaging helps to lower the maintenance burden across Fedora's Haskell packages.

This is the main page for the Fedora Diversity [[FAD]], which focuses on reviewing and finishing our current goa ...composes Fedora and the unique needs and wishes of the groups that make up Fedora. Since our team is new, we plan to accomplish primary and secondary goals o

* In any case, this speaks to 1) infrastructure 2) use of the Fedora 'brand' (including possibly the trademarks) 3) the goals of the project its ...ng to solve this problem are--could it negatively impact existing parts of Fedora that are currently functioning well?