Bug 619908 – media-gfx/darktable: make postinst upgrade/downgrade warning more generic

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Micha 2017-05-28 07:16:34 UTC]

Currently darktable-2.2.3 is stable and 2.2.4 is most recent version.
But both ebuilds say that 1.6 is currently stable. 1.6 is outdated.
1) Thats not correct.
2) I suggest to show these warnings only when upgrading from 1.6. Is that possible?
(2.x started end of 2015.)


Reproducible: Always

Steps to Reproduce:
1.emerge darktable
2.
3.

[Comment 1 Micha 2017-05-28 07:17:17 UTC]

pkg_postinst() {
        gnome2_icon_cache_update
        fdo-mime_desktop_database_update

        elog "when updating from the currently stable 1.6 series,"
        elog "please bear in mind that your edits will be preserved during this process,"
        elog "but it will not be possible to downgrade from 2.0 to 1.6 any more."
        echo
        ewarn "It will not be possible to downgrade!"
}

[Comment 2 Lebedev Roman 2017-05-28 18:39:37 UTC]

(In reply to Micha from comment #1)
> pkg_postinst() {
>         gnome2_icon_cache_update
>         fdo-mime_desktop_database_update
> 
>         elog "when updating from the currently stable 1.6 series,"
That is valid for each and every upgrade between major releases of darktable, i.e.
1.6 -> 2.0
1.6 -> 2.2
2.0 -> 2.2
etc, you get the idea.

>         elog "please bear in mind that your edits will be preserved during
> this process,"
>         elog "but it will not be possible to downgrade from 2.0 to 1.6 any
> more."
>         echo
>         ewarn "It will not be possible to downgrade!"
> }

[Comment 3 Micha 2017-05-29 10:33:30 UTC]

(In reply to Lebedev Roman from comment #2)
> That is valid for each and every upgrade between major releases of
> darktable, i.e.
> 1.6 -> 2.0
> 1.6 -> 2.2
> 2.0 -> 2.2
> etc, you get the idea.
Yes, maybe that should be it postinst instructions.
But saying 1.6 is the current stable version should be removed.

[Comment 4 Marek Szuba (RETIRED) 2020-06-18 15:37:30 UTC]

Come to think of it, we'll likely get 3.0.2 - in which the message in question has already been made more generic - stabilised soon so I do not think I'll bother changing this in 2.6.2.