Re: Fedora "backports" repo? (Was Re: PostgreSQL 9 for F14?)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 22, 2010 at 3:59 PM, Al Dunsmuir <al.dunsmuir@xxxxxxxxxxxx> wrote:
> On Wednesday, September 22, 2010, 8:06:12 AM, drag01 wrote:
>> On Wed, Sep 22, 2010 at 11:24 AM, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>>> On Mon, Sep 20, 2010 at 09:58:53PM -0400, Arthur Pemberton wrote:
>>>> 2010/9/20 MichaÅ Piotrowski <mkkp4x4@xxxxxxxxx>:
>>>> > 2010/9/21 Toshio Kuratomi <a.badger@xxxxxxxxx>:
>>>> >> As the concept of using third party repositories (both as packagers and as
>>>> >> users) grows, this interdependence will grow.
>>>> >
>>>> > Ok, so maybe it's time to setup Fedora "backports" repo for these that
>>>> > wants new and shiny Firefox 4, PostgreSQL 9 or whatever with big
>>>> > number.
>>>>
>>>>
>>>> What exactly is the fear here with these updates? Are there many
>>>> desktop users who do NOT want the latest released Firefox? Are there
>>>> many people using Fedora as their OS for their database server?
>>>
>>> Maybe we should turn this around and ask why more people don't
>>> use Rawhide.
>
>> Well "use rawhide" for anything else than testing and/or developing
>> the new release just do not fly.
>
>> Some of the reasons I can think of:
>
>> 1) To high rate of changes / breakage
>
> These are two separate issues.
>
> Change:
> Without Âchange in Fedora, Âwe Âmight Âas well turn off the lights.

You missed the point.

>> 3) Slower kernel
>
> On purpose - first you get things right, then you get them fast. Those
> additional Âchecks Âare important so that any issues are identified as
> soon as possible.

You missed the point.

> You want to benchmark something? ÂBuild a no-debug kernel.

You missed the point.

>> 4) To much of "manual fixing" required
>
> Maybe Âreduced with a bit of focus, but likely also part of the nature
> of the beast.

You missed the point.

>> 5) To many broken deps, which might prevent applying updates and security fixes
>
> This one autoqa should be able to solve. ÂReduces breakage in general,
> and Âhelps Âensure Âthat Âbreakage Âin branched releases is identified
> sooner.
>
>> 6) Some others that I can't think of right now might be a consequence
>> of the above or something else
>
> Stuff Âhappens, Âbut ÂRawhide Âis the place for it to happen.

You missed the point.

> ÂBut not
> gratuitously Â- Âthat's Ânot Âbeing Ânice Âto Âyour fellow Fedora team
> members.

Again, you missed the point.

I did not say "rawhide SUCKS!!!!!1111!!!"" I said that rawhide's
purpose is for development and testing but NOT for general use.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux