How do we release dependent libraries for digiKam-5.0.0-beta1?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

How do we release dependent libraries for digiKam-5.0.0-beta1?

Alexander Potashev
Hi everyone,
(Luigi pushed me a lot so I finally start this discussion ;))

digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
its dependencies (KF5-based versions of libraries) at least as
alpha/beta versions before that date:
    1. libkipi (currently in KDE Applications)
    2. libkface (currently in KDE Applications)
    3. libkexiv2 (currently in KDE Applications)
    4. libkdcraw (currently in KDE Applications)
    5. libksane (currently in KDE Applications)
    6. libkvkontakte (currently in extragear-libs)
    7. libmediawiki (currently in extragear-libs)

As listed above, many of these dependent libraries are currently part
of KDE Applications, for example in KDE Applications 15.08.x we have
kdelibs4-based editions of all 5 relevant libraries from the above
list.

I see two ways of releasing the 7 libraries mentioned above:
 Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
release of KDE Applications 15.12.x before October 18th. libkvkontakte
and libmediawiki should also be released before that date, but they
are not tied to KDE Applications release schedule. (Btw, is it OK if
digikam-beta depends on kde-apps-alpha?)
 Plan 2: Move all these 7 libraries (their KF5-based versions) into
extragear-libs and release them.

Please tell us if any of these plans works better for you than the
other, and why. Everyone are welcome to share their thoughts -
packagers, KDE Apps release team, developers, etc.

--
Alexander Potashev
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: How do we release dependent libraries for digiKam-5.0.0-beta1?

Jeremy Whiting
From a release team perspective I don't think we can/should move
libraries that are currently part of KDE Applications already to
extragear. We usually release applications with their dependencies
(except frameworks) at the same time. Releasing libkexiv2 from
extragear while okular in Applications uses it seems backwards to me.
Are all 5 of the libraries that are released with KDE Applications
used by applications that are also released with KDE Applications?

BR,
Jeremy

On Wed, Sep 23, 2015 at 4:28 PM, Alexander Potashev
<[hidden email]> wrote:

> Hi everyone,
> (Luigi pushed me a lot so I finally start this discussion ;))
>
> digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
> its dependencies (KF5-based versions of libraries) at least as
> alpha/beta versions before that date:
>     1. libkipi (currently in KDE Applications)
>     2. libkface (currently in KDE Applications)
>     3. libkexiv2 (currently in KDE Applications)
>     4. libkdcraw (currently in KDE Applications)
>     5. libksane (currently in KDE Applications)
>     6. libkvkontakte (currently in extragear-libs)
>     7. libmediawiki (currently in extragear-libs)
>
> As listed above, many of these dependent libraries are currently part
> of KDE Applications, for example in KDE Applications 15.08.x we have
> kdelibs4-based editions of all 5 relevant libraries from the above
> list.
>
> I see two ways of releasing the 7 libraries mentioned above:
>  Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
> release of KDE Applications 15.12.x before October 18th. libkvkontakte
> and libmediawiki should also be released before that date, but they
> are not tied to KDE Applications release schedule. (Btw, is it OK if
> digikam-beta depends on kde-apps-alpha?)
>  Plan 2: Move all these 7 libraries (their KF5-based versions) into
> extragear-libs and release them.
>
> Please tell us if any of these plans works better for you than the
> other, and why. Everyone are welcome to share their thoughts -
> packagers, KDE Apps release team, developers, etc.
>
> --
> Alexander Potashev
> _______________________________________________
> release-team mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/release-team
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: How do we release dependent libraries for digiKam-5.0.0-beta1?

Jeremy Whiting
One other thing to note. All 5 of those libraries that are released
with KDE Applications are kdelibs4/qt4 based on their master branches
currently. To release them with KDE Applications 15.12 they need the
frameworks branches merged to master branch.

On Wed, Sep 23, 2015 at 4:48 PM, Jeremy Whiting <[hidden email]> wrote:

> From a release team perspective I don't think we can/should move
> libraries that are currently part of KDE Applications already to
> extragear. We usually release applications with their dependencies
> (except frameworks) at the same time. Releasing libkexiv2 from
> extragear while okular in Applications uses it seems backwards to me.
> Are all 5 of the libraries that are released with KDE Applications
> used by applications that are also released with KDE Applications?
>
> BR,
> Jeremy
>
> On Wed, Sep 23, 2015 at 4:28 PM, Alexander Potashev
> <[hidden email]> wrote:
>> Hi everyone,
>> (Luigi pushed me a lot so I finally start this discussion ;))
>>
>> digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
>> its dependencies (KF5-based versions of libraries) at least as
>> alpha/beta versions before that date:
>>     1. libkipi (currently in KDE Applications)
>>     2. libkface (currently in KDE Applications)
>>     3. libkexiv2 (currently in KDE Applications)
>>     4. libkdcraw (currently in KDE Applications)
>>     5. libksane (currently in KDE Applications)
>>     6. libkvkontakte (currently in extragear-libs)
>>     7. libmediawiki (currently in extragear-libs)
>>
>> As listed above, many of these dependent libraries are currently part
>> of KDE Applications, for example in KDE Applications 15.08.x we have
>> kdelibs4-based editions of all 5 relevant libraries from the above
>> list.
>>
>> I see two ways of releasing the 7 libraries mentioned above:
>>  Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
>> release of KDE Applications 15.12.x before October 18th. libkvkontakte
>> and libmediawiki should also be released before that date, but they
>> are not tied to KDE Applications release schedule. (Btw, is it OK if
>> digikam-beta depends on kde-apps-alpha?)
>>  Plan 2: Move all these 7 libraries (their KF5-based versions) into
>> extragear-libs and release them.
>>
>> Please tell us if any of these plans works better for you than the
>> other, and why. Everyone are welcome to share their thoughts -
>> packagers, KDE Apps release team, developers, etc.
>>
>> --
>> Alexander Potashev
>> _______________________________________________
>> release-team mailing list
>> [hidden email]
>> https://mail.kde.org/mailman/listinfo/release-team
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: How do we release dependent libraries for digiKam-5.0.0-beta1?

Albert Astals Cid
In reply to this post by Alexander Potashev
El Dijous, 24 de setembre de 2015, a les 01:28:14, Alexander Potashev va
escriure:

> Hi everyone,
> (Luigi pushed me a lot so I finally start this discussion ;))
>
> digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
> its dependencies (KF5-based versions of libraries) at least as
> alpha/beta versions before that date:
>     1. libkipi (currently in KDE Applications)
>     2. libkface (currently in KDE Applications)
>     3. libkexiv2 (currently in KDE Applications)
>     4. libkdcraw (currently in KDE Applications)
>     5. libksane (currently in KDE Applications)
>     6. libkvkontakte (currently in extragear-libs)
>     7. libmediawiki (currently in extragear-libs)
>
> As listed above, many of these dependent libraries are currently part
> of KDE Applications, for example in KDE Applications 15.08.x we have
> kdelibs4-based editions of all 5 relevant libraries from the above
> list.

Important question, are the KF5-versions of those libraries co-installable
with the kdelibs4-versions?

>
> I see two ways of releasing the 7 libraries mentioned above:
>  Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
> release of KDE Applications 15.12.x before October 18th.

I don't think that is on the plan for us, the KDE Applications 15.12 schedule
starts much later
https://techbase.kde.org/Schedules/Applications/15.12_Release_Schedule

> libkvkontakte
> and libmediawiki should also be released before that date, but they
> are not tied to KDE Applications release schedule. (Btw, is it OK if
> digikam-beta depends on kde-apps-alpha?)
>  Plan 2: Move all these 7 libraries (their KF5-based versions) into
> extragear-libs and release them.

If the libraries are co-installable with their kdelibs4 counterparts and if
digikam 5.0 final is planned to happen after we release KDE Applications 15.12
I guess you could release an "unofficial tarball" of those libraries clearly
marked with a a weird number like 15.11.55 or something, with the
understanding that you'll stop releasing those applications after the KDE
Applications 15.12 release (assuming we decide to migrate those libs to KF5-
based, which i guess makes sense).

Cheers,
  Albert

>
> Please tell us if any of these plans works better for you than the
> other, and why. Everyone are welcome to share their thoughts -
> packagers, KDE Apps release team, developers, etc.

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: How do we release dependent libraries for digiKam-5.0.0-beta1?

Alexander Potashev
2015-09-24 2:18 GMT+03:00 Albert Astals Cid <[hidden email]>:

> El Dijous, 24 de setembre de 2015, a les 01:28:14, Alexander Potashev va
> escriure:
>> Hi everyone,
>> (Luigi pushed me a lot so I finally start this discussion ;))
>>
>> digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
>> its dependencies (KF5-based versions of libraries) at least as
>> alpha/beta versions before that date:
>>     1. libkipi (currently in KDE Applications)
>>     2. libkface (currently in KDE Applications)
>>     3. libkexiv2 (currently in KDE Applications)
>>     4. libkdcraw (currently in KDE Applications)
>>     5. libksane (currently in KDE Applications)
>>     6. libkvkontakte (currently in extragear-libs)
>>     7. libmediawiki (currently in extragear-libs)
>>
>> As listed above, many of these dependent libraries are currently part
>> of KDE Applications, for example in KDE Applications 15.08.x we have
>> kdelibs4-based editions of all 5 relevant libraries from the above
>> list.
>
> Important question, are the KF5-versions of those libraries co-installable
> with the kdelibs4-versions?
>
>>
>> I see two ways of releasing the 7 libraries mentioned above:
>>  Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
>> release of KDE Applications 15.12.x before October 18th.
>
> I don't think that is on the plan for us, the KDE Applications 15.12 schedule
> starts much later
> https://techbase.kde.org/Schedules/Applications/15.12_Release_Schedule
>
>> libkvkontakte
>> and libmediawiki should also be released before that date, but they
>> are not tied to KDE Applications release schedule. (Btw, is it OK if
>> digikam-beta depends on kde-apps-alpha?)
>>  Plan 2: Move all these 7 libraries (their KF5-based versions) into
>> extragear-libs and release them.
>
> If the libraries are co-installable with their kdelibs4 counterparts and if
> digikam 5.0 final is planned to happen after we release KDE Applications 15.12
> I guess you could release an "unofficial tarball" of those libraries clearly
> marked with a a weird number like 15.11.55 or something, with the
> understanding that you'll stop releasing those applications after the KDE
> Applications 15.12 release (assuming we decide to migrate those libs to KF5-
> based, which i guess makes sense).

Hi Albert, Jeremy,

libkipi and libkdcraw are not co-installable because icons are
installed in the same place as in their kdelibs4 versions
(/usr/share/icons/hicolor/*/apps/{kipi,kdcraw}.png).

Here is how these libraries are used by KDE Applications:
    libkipi: gwenview, spectacle, ksnapshot (kdelibs4)
    libkface: <none>
    libkexiv2: okular, kdegraphics-thumbnailers (kdelibs4)
    libkdcraw: gwenview, kdegraphics-thumbnailers (kdelibs4)
    libksane: ksaneplugin (kdelibs4)

There is little left to do until we can drop libkipi/kdelibs4 and
libkdcraw/kdelibs4 from KDE Applications 15.12:
 - Move KSnapshot to extragear,
 - Have kdegraphics-thumbnailers ported to KF5 in KDE Applications 15.12.

--
Alexander Potashev
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: How do we release dependent libraries for digiKam-5.0.0-beta1?

Albert Astals Cid
El Dijous, 24 de setembre de 2015, a les 17:49:56, Alexander Potashev va
escriure:

> 2015-09-24 2:18 GMT+03:00 Albert Astals Cid <[hidden email]>:
> > El Dijous, 24 de setembre de 2015, a les 01:28:14, Alexander Potashev va
> >
> > escriure:
> >> Hi everyone,
> >> (Luigi pushed me a lot so I finally start this discussion ;))
> >>
> >> digiKam-5.0.0-beta1 is planned for October 18th, so we need to release
> >> its dependencies (KF5-based versions of libraries) at least as
> >>
> >> alpha/beta versions before that date:
> >>     1. libkipi (currently in KDE Applications)
> >>     2. libkface (currently in KDE Applications)
> >>     3. libkexiv2 (currently in KDE Applications)
> >>     4. libkdcraw (currently in KDE Applications)
> >>     5. libksane (currently in KDE Applications)
> >>     6. libkvkontakte (currently in extragear-libs)
> >>     7. libmediawiki (currently in extragear-libs)
> >>
> >> As listed above, many of these dependent libraries are currently part
> >> of KDE Applications, for example in KDE Applications 15.08.x we have
> >> kdelibs4-based editions of all 5 relevant libraries from the above
> >> list.
> >
> > Important question, are the KF5-versions of those libraries co-installable
> > with the kdelibs4-versions?
> >
> >> I see two ways of releasing the 7 libraries mentioned above:
> >>  Plan 1: Keep the first 5 ones in KDE Applications and make an alpha
> >>
> >> release of KDE Applications 15.12.x before October 18th.
> >
> > I don't think that is on the plan for us, the KDE Applications 15.12
> > schedule starts much later
> > https://techbase.kde.org/Schedules/Applications/15.12_Release_Schedule
> >
> >> libkvkontakte
> >> and libmediawiki should also be released before that date, but they
> >> are not tied to KDE Applications release schedule. (Btw, is it OK if
> >> digikam-beta depends on kde-apps-alpha?)
> >>
> >>  Plan 2: Move all these 7 libraries (their KF5-based versions) into
> >>
> >> extragear-libs and release them.
> >
> > If the libraries are co-installable with their kdelibs4 counterparts and
> > if
> > digikam 5.0 final is planned to happen after we release KDE Applications
> > 15.12 I guess you could release an "unofficial tarball" of those
> > libraries clearly marked with a a weird number like 15.11.55 or
> > something, with the
> > understanding that you'll stop releasing those applications after the KDE
> > Applications 15.12 release (assuming we decide to migrate those libs to
> > KF5- based, which i guess makes sense).
>
> Hi Albert, Jeremy,
>
> libkipi and libkdcraw are not co-installable because icons are
> installed in the same place as in their kdelibs4 versions
> (/usr/share/icons/hicolor/*/apps/{kipi,kdcraw}.png).

What about the library names? Icons colliding is not great but i'm sure
packagers can find a way around it.

Cheers,
  Albert
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel