[Lunar-commits] <moonbase> firefox4: removed because it is not security supported - use firefox5

[samuel]

No.

The only proper way to fix is, is move firefox to firefox3 and let the
module firefox track the major version bumps... only extension freaks
need 3.x.x so that's a minority... At least that fixes the firefox
module for the majority.

what you are doing, creating new modules and removing old ones asap is
ridiculous.

gr,s.

On Fri, Jul 1, 2011 at 1:54 AM, Zbigniew Luszpinski <zbiggy at o2.pl> wrote:
>> Is there actually a *good* reason to keep the 'old' firefox version
>> alive ? I mean the 3.x.x series? Can't we just move the firefox5
>> module into the firefox module? Cause otherwise we will have this
>> removing of firefox_x every 6 weeks from now on...
>
> The 'old' Firefox 3.6.18 is actually new: released June 21st, 2011 and
> still maintained (but not for long as Mozilla says). Mainly because of
> extensions which are not firefox5 ready yet. Extensions maniacs would be
> crazy if firefox module would be zdeprecated or updated to firefox5. That
> is why Mozilla and we keep it updating.
>
> It looks Mozilla likes the way Google Chrome is developed: major versions
> bump every 3 months so the problem will be going back from time to time.
> The only way to fix it is to create any way of upgrade paths which will
> tell lunar which module is upgrade for removed one.
>
> have a nice day,
> Zbigniew Luszpinski
>
>> On Thu, Jun 30, 2011 at 9:07 AM, Duncan Gibson <duncan.gibson at xs4all.nl>
> wrote:
>> >> commit f81cfd86a2654eea3338d7ba79b491b481783a82
>> >> Author: Zbigniew Luszpinski <zbiggy at lunar-linux.org>
>> >> Date:   Thu Jun 30 01:22:35 2011 +0200
>> >>
>> >>     firefox4: removed because it is not security supported - use
>> >> firefox5
>> >
>> > Maybe it would have been better if this had been moved to zdeprecated
>> > for a while so people had a chance to switch before it was removed.
>> >
>> > Or temporarily turn firefox4 into a profile that pulls in firefox5
>> > instead.
>> >
>> > Sometimes it's a pain in the bum when active modules get deleted or
>> > renamed because the next time you 'lunar update' or even just 'lin
>> > moonbase' the system has no clue about the old module name any more.
>> >
>> > Not everyone is using a moonbase.git and can backtrack while cleaning
>> > up.
>> >
>> > D.
>> >
>> > _______________________________________________
>> > Lunar-dev mailing list
>> > Lunar-dev at lunar-linux.org
>> > http://foo-projects.org/mailman/listinfo/lunar-dev
>>
>> _______________________________________________
>> Lunar-dev mailing list
>> Lunar-dev at lunar-linux.org
>> http://foo-projects.org/mailman/listinfo/lunar-dev
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev
>