[PATCH] module upgrade table - no more troubles with legacy modules removed

samuel samuel.verstraete at gmail.com
Sat Aug 20 22:30:30 CEST 2011


you should fix your modules instead of the tools...

On Sat, Aug 20, 2011 at 8:59 PM, Zbigniew Luszpinski <zbiggy at o2.pl> wrote:
> Hello,
>
> here is module upgrade patch I made. Please commit it because I have no
> write access to lunar.git.
>
> How Lunar core tools looks now:
> when legacy module is removed from moonbase Lunar asks if you want to
> remove it (default: yes) or keep it. This way when you sleep lunar update
> will silently cut some old modules. In my case this was kde3 - I woke up
> and surprise I have no desktop :(.
>
> How Lunar core tools behave after this patch:
> Lunar will check modules upgrade table if there is upgrade path. If it is
> present new module will be lined. If you are watching lunar update it will
> ask you if you wnat to upgrade. Default is yes so when firefox5 will be
> removed and lunar is updating when you are sleeping you will wake up next
> day with firefox 6.0 ready for work. If you say no default previous
> behaviour takes action (default remove - if no leave).
>
> Info for module developers:
> Module upgrade table is inside moonbase file named: upgrade.tbl in root
> directory of the moonbase. You have access to it via moonbase.git
>
> File format is easy:
> removed_module new_module
> for example:
> firefox4 firefox5
>
> firefox5 and thunderbird5 were removed from moonbase because of end of
> life. If you have them installed and have this patch applied do lunar
> update to test the solution. firefox5 will be upgraded to firefox6 and
> thunderbird5 will be upgraded to thunderbird6.
>
>
> have a nice day,
> Zbigniew Luszpinski
>
> _______________________________________________
> Lunar-dev mailing list
> Lunar-dev at lunar-linux.org
> http://foo-projects.org/mailman/listinfo/lunar-dev
>


More information about the Lunar-dev mailing list