Am Donnerstag 20 August 2009 schrieb Jesse Keating:
On Thu, 2009-08-20 at 10:47 +0000, Jeroen van Meeuwen wrote:
> fedora-livecd-kde.ks | 3 +++
> 1 file changed, 3 insertions(+)
>
> New commits:
> commit ef477aff8673d236b61a92f02fd19320fc85d999
> Author: Sebastian Vahl <fedora(a)deadbabylon.de>
> Date: Tue Aug 18 16:33:55 2009 +0200
>
> use yum-presto by default (like on gnome spin:
>
https://www.redhat.com/archives/fedora-devel-list/2009-August/msg00932.ht
>ml)
>
> diff --git a/fedora-livecd-kde.ks b/fedora-livecd-kde.ks
> index 66d12e8..99adaf0 100644
> --- a/fedora-livecd-kde.ks
> +++ b/fedora-livecd-kde.ks
> @@ -42,6 +42,9 @@ fuse
> liveusb-creator
> #pavucontrol # nice to have but pulls in gstreamer
(~3
megs)
>
> +# use yum-presto by default
> +yum-presto
> +
>
> ### fixes and space issues
>
>
>
> _______________________________________________
> spin-kickstarts-commits mailing list
> spin-kickstarts-commits(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/spin-kickstarts-commits
This was not done in time, and was not in the Alpha compose I did.
Then when was the time you did the compose? I've created the bug on Tue, 18.
Jeroen included it in the F12Alpha-tree on Thu, 20. So is this maybe just a
problem in talking to each other (I can't remember the correct english phrase
atm, It's too late here :) ).
I think we need a general guideline for this. And also a special (private?)
notice for all spin maintainers when their "spin" will be composed. Since
I'm
doing the KDE live images one question always was, when the final spin will be
composed and until which deadline I have to commit my changes. The general
freeze date is normally not an option for "spin" maintainers because many
changes will be committed after the freeze when rawhide is more stabilized.
This change was a quite small one and would cause no problems. But they're
might be bigger ones...
Sebastian