Rex Dieter wrote:
> Agreed, we'll have to revisit it with fc17 (or f16+) with the
> finer-grained package splitting going on.
I actually think anything KDE-related should be dropped from critpath with
no replacement.
We've been working fine for years without critpath actually being enforced
on
Kevin Kofler wrote:
> Adam Jackson wrote:
>> kdebase pulls in the world, film at 11.
>
> IMHO we really need to remove kde* from critpath, it just doesn't scale.
Agreed, we'll have to revisit it with fc17 (or f16+) with the finer-grained
package splitting going on.
-- rex
--
devel mailing li
Adam Jackson wrote:
> kdebase pulls in the world, film at 11.
IMHO we really need to remove kde* from critpath, it just doesn't scale.
Kevin Kofler
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
On Wed, 2012-01-11 at 10:32 -0500, Paul W. Frields wrote:
> https://admin.fedoraproject.org/pkgdb/acls/name/qrencode
>
> Is this package supposed to be critical path?[1] It's marked that way
> for f16 and devel branch, but it was surprising to me.
[ajax@f17 ~]$ repoquery --whatrequires qrencode
g
https://admin.fedoraproject.org/pkgdb/acls/name/qrencode
Is this package supposed to be critical path?[1] It's marked that way
for f16 and devel branch, but it was surprising to me.
* * *
[1] https://fedoraproject.org/wiki/Critical_Path_Packages
--
Paul W. Frields
