<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<br>
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA256<br>
<br>
Can we just drop comps entirely (or at least trim them down
significantly)? I know that this will not happen from day to day,
but I see the comps just as an ugly workaround for missing weak
dependencies, which we have now.<br>
<br>
<br>
Vít<br>
<br>
<br>
<br>
<br>
Dne 10.7.2015 v 14:05 Stephen Gallagher napsal(a):<br>
<span style="white-space: pre;">> (Please keep the conversation
on the devel list; I'm CCing it the rel<br>
> -eng list to make sure all the relevant people see the
initial message)<br>
><br>
> This past week, the Fedora Packaging Committee approved the
use of<br>
> "weak dependencies" in Fedora. What this means is that RPM
packages can<br>
> now have three levels of dependency-resolution: Requires,
Recommends<br>
> and Suggests.<br>
> * Requires: the requested package cannot function without
this<br>
> additional package installed<br>
> * Recommends: the requested package can function in some
minimal<br>
> capacity without this additional package installed, but the
majority of<br>
> installations will want it for full productivity. These are
usually<br>
> core plugins for the primary package. DNF defaults to
installing<br>
> Recommends: dependencies automatically.<br>
> * Suggests: the requested package can easily function
without this<br>
> additional package. This module may provide some less-common<br>
> functionality that a user might want. DNF defaults to *not*
installing<br>
> Suggests: packages automatically.<br>
><br>
> Traditionally, we have only supported "Requires" dependencies
and thus<br>
> the creation of install media (Live and otherwise) has been
relatively<br>
> straightforward: we create a kickstart file that is fed into
the<br>
> compose process containing a list of packages and groups that
we want<br>
> installed onto the target system and the compose process
automatically<br>
> pulls in all of the dependencies. However, with the advent of
weak<br>
> dependencies, we have new questions that need answering about
how this<br>
> compose process should work. (We also need to investigate
what exactly<br>
> happens with the tools we have today - some of which still
use yum, not<br>
> DNF - when weak dependencies are added to the mix).<br>
><br>
> From my perspective, there are three ways that we could
choose to go:<br>
><br>
> 1) Follow the default DNF behavior: Requires: and Recommends:
packages<br>
> are included on the install media (and therefore also
installed<br>
> together onto the target system)<br>
><br>
> 2) Include *all* dependencies - Requires, Recommends and
Suggests - on<br>
> the install media. The installer would still follow DNF
defaults, so<br>
> the target system would get only the Requires and Recommends
packages<br>
> unless the Suggests: packages are explicitly selected (which
will also<br>
> require the creation of additional comps.xml changes to
include the<br>
> Suggests packages)<br>
><br>
> 3) Include only Requires: dependencies by default and require
spin<br>
> -kickstarts owners to explicitly add any Recommends or
Suggests<br>
> packages that they also want to include. Packages added
explicitly will<br>
> be installed as described in 2) (requiring additional
comps.xml changes<br>
> to include Suggests stuff)<br>
><br>
><br>
> Note that at the moment, DNF itself does not have a
configuration<br>
> option to tweak the default install behavior, so 'dnf
install'<br>
> effectively treats Recommends the same way as Requires (but
'dnf<br>
> remove' will treat them differently, of course). I discussed
this with<br>
> the DNF developers this morning and they hope to have a
configuration<br>
> option and/or command-line argument available to change this
behavior<br>
> before Beta Freeze, so we should still be able to ship F23
with any of<br>
> the above options.<br>
><br>
> I think the best time to make these decisions is now, well in
advance<br>
> of the Alpha Freeze so we have time to make adjustments as
needed.<br>
> Thank you for reading to the end, I know the above has been a
wall-o'<br>
> -text.<br>
><br>
></span><br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2<br>
<br>
iQIcBAEBCAAGBQJVpMSzAAoJEAzgnueZF7h8epkP/0LH9wzwx5XjS41lOnG3cr5C<br>
2O5fEOwODffCa6une0tiJDTLvXLyx9BthEKClRHImpNFEVXg9QGGYurWbqhRfeJA<br>
Zvc1Wzuvlf2s5iNEMFw7c8S1s3FK4/ytX4hMSx5F/9RAENq/qKxKEUU6BjiP6RxF<br>
qP7e5yaN+y6QEuogWe2j4caqD/mfP8ZhanrvHO/KAOv8a+OAp0LZXF4uuHbfxfak<br>
0OJw2/q9oKoO8ww5CiNJdRk+vMEXnIOT9XzMdqcpV5/GzKt42wNFqusT84Shvih2<br>
nl2PB6Wh1rPL8oUwmQsWToEpoN0Zjh7FDVqZcbn4ja7depmJ0ub0cNTl4eJ+1AJc<br>
fc5c+pZ5qLUKokTOvk708yy5pq2HbByqBTeBHxG51YwLZd2bUlZBQbyfadfM66Z3<br>
FzyiEEjxA+V/mm0VXoA1kuEN1+8BnW25atifnvTLcGs5doGnEivDogaCDi8GDdCt<br>
dR/ZLPCJySNcZJPROfrlKWd6PSUfX/M3bzdaBJcIQL/klO45dYTGolxyr0R/Muf5<br>
B/apLMsVTyLE8Qp4HpmcmjKft1rgXNAHpe3EyXD39dhrtbpmZyMYwjO029yYAi6R<br>
tQa2ISnuQO1hMv78A5KhseKMyHv4XKgeMaXwwdpKExZh2u8otgCBZXYq/G7MiMWc<br>
3UQOteXvXhgWXjW5y7m4<br>
=EPjN<br>
-----END PGP SIGNATURE-----<br>
<br>
</body>
</html>