PR#10: adding in how to enable modules & supported package managers - fedora-docs/modularity

fedora-docs / modularity

#10 adding in how to enable modules & supported package managers

Merged 5 years ago by asamalik. Opened 5 years ago by langdon.

fedora-docs/ langdon/modularity how-to-get into master

adding in how to enable modules & supported package managers and fixed line breaks after period per adoc best practices

langdon • 5 years ago

7debc63

en-US/Using_Modules.adoc

file modified

+25 -1

		`@@ -6,6 +6,29 @@`

		`From the user perspective, modules are like release-independent package groups on independent lifecycles, providing alternative streams of content to Fedora.`

		`+ == Enable modular repositories`
		`+`
		`+ If you are running the Fedora Server Edition, the Modular Repository should already be enabled.`
		`+ However, if you are using a container or a different Edition, you need to:`
		`+`
		`+ # dnf install fedora-repos-modular`
		`+`
		`+ == Supported / Unsupported Package Managers`
		`+`
		`+ * Supported`
		`+ ** dnf`
		`+ ** dnfdragora`
		`+ * Unsupported (if unlisted, assume unsupported)`
		`+ ** microdnf`
		`+ ** PackageKit`
		`+ ** Gnome Software`
		`+ ** Apper`
		`+ ** Cockpit`
		`+`
		`+ Using an unsupported Package Manager for any reason with modules enabled has serious potential to break things.`
		`+ People are working on the above list of Unsupported package managers primarily by including module support in libdnf.`
		`+ If you are interested in adding module support to a different package manager, please contact the https://github.com/rpm-software-management/dnf[dnf team].`
		`+`
		`== List available modules`

		`To list all available modules and their streams, run the following command:`
		`@@ -31,7 +54,8 @@`

		`== Module defaults`

		`- We are currently working on _system profiles_ — the defaults for your system. Thanks to these, you will need to be specific about the module, stream, or profile only when you need to. When implemented, all the following commands will also work:`
		`+ We are currently working on _system profiles_ — the defaults for your system.`
		`+ Thanks to these, you will need to be specific about the module, stream, or profile only when you need to. When implemented, all the following commands will also work:`

		`$ dnf install nodejs # installs a nodejs RPM package from the default stream`
		`$ dnf module install nodejs # installs the default profile from the default stream`

no initial comment

langdon commented 5 years ago

@sgallagh @asamalik please review

sgallagh commented on line 22 of en-US/Using_Modules.adoc 5 years ago

I would note that work is in progress to correct this. Otherwise, LGTM.

zbyszek commented on line 23 of en-US/Using_Modules.adoc 5 years ago

Maybe also mention cockpit in the unsupported list.

zbyszek commented on line 9 of en-US/Using_Modules.adoc 5 years ago

This is not enough, because the repos are disabled.

dnf config-manager --set-enabled fedora-modular fedora-modular-updates

james commented on line 21 of en-US/Using_Modules.adoc 5 years ago

We may want another category for things that aren't ever going to get fixed.

We still ship the "yum" package with the yum-deprecated command, if you aren't using modules that works fine. We also ship zypper package, apt package and smart package. May also need to mention spacewalk/satellite?

sgallagh commented 5 years ago

@zbyszek I don't know why you think that. They are enabled by default if you have the repo package installed. I just confirmed.

I agree, include Cockpit in the list explicitly.

sgallagh commented 5 years ago

@james I think "if unlisted, assume unsupported" covers that.

zbyszek commented 5 years ago