-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Recommended reading: https://fedorahosted.org/fesco/ticket/1517
The original request to FESCo was for a decision on whether a package built in COPR could `Requires: rpmfusion-foo` from RPMFusion. However, with the new availability of weak dependencies, I've expanded the discussion to include whether it would be acceptable in COPR or Fedora proper to use `Recommends: rpmfusion-foo` or `Suggests: rpmfusion-foo`.
If we decide that the weak dependencies are acceptable, this would make it much easier for users to install codecs, etc. from RPMFusion (always assuming of course that they are legally permitted to do so wherever they are). In effect, it would become possible to do this easily at install-time because just adding the RPMFusion repos manually in the installer could then result in pulling in Recommended codecs.
I figure this is of particular interest to the Workstation SIG, so I'm raising it here.
On Fri, Dec 18, 2015 at 8:15 AM, Stephen Gallagher sgallagh@redhat.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Recommended reading: https://fedorahosted.org/fesco/ticket/1517
The original request to FESCo was for a decision on whether a package built in COPR could `Requires: rpmfusion-foo` from RPMFusion. However, with the new availability of weak dependencies, I've expanded the discussion to include whether it would be acceptable in COPR or Fedora proper to use `Recommends: rpmfusion-foo` or `Suggests: rpmfusion-foo`.
If we decide that the weak dependencies are acceptable, this would make it much easier for users to install codecs, etc. from RPMFusion (always assuming of course that they are legally permitted to do so wherever they are). In effect, it would become possible to do this easily at install-time because just adding the RPMFusion repos manually in the installer could then result in pulling in Recommended codecs.
I figure this is of particular interest to the Workstation SIG, so I'm raising it here.
Ha, I had the same thought and you've beat me to it. Well done.
josh
William Moreno Reyes http://about.me/williamjmorenor
2015-12-18 7:15 GMT-06:00 Stephen Gallagher sgallagh@redhat.com:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Recommended reading: https://fedorahosted.org/fesco/ticket/1517
The original request to FESCo was for a decision on whether a package built in COPR could `Requires: rpmfusion-foo` from RPMFusion. However, with the new availability of weak dependencies, I've expanded the discussion to include whether it would be acceptable in COPR or Fedora proper to use `Recommends: rpmfusion-foo` or `Suggests: rpmfusion-foo`.
I am +100 to use rpm fusion weak depencies in Fedora Package, or at less in Corp Builds.
If we decide that the weak dependencies are acceptable, this would make it much easier for users to install codecs, etc. from RPMFusion (always assuming of course that they are legally permitted to do so wherever they are). In effect, it would become possible to do this easily at install-time because just adding the RPMFusion repos manually in the installer could then result in pulling in Recommended codecs.
I figure this is of particular interest to the Workstation SIG, so I'm raising it here. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iEYEARECAAYFAlZ0BtYACgkQeiVVYja6o6OqMwCeKMLk/+AtuOlGrFgr32DxsnrF frUAn0Kt7m+mA1xJltshROxdCsTuiZV5 =tzS2
-----END PGP SIGNATURE-----
desktop mailing list desktop@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/desktop@lists.fedoraproject.org
https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail Este correo electrónico se ha enviado desde un equipo libre de virus y protegido por Avast. www.avast.com https://www.avast.com/?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
desktop@lists.stg.fedoraproject.org
-
Josh Boyer -
Stephen Gallagher -
William Moreno