Re: Heads-up: KContacts and KCalendarCore about to move to Frameworks
On Thursday, 19 September 2019 21:40:19 CEST Luigi Toscano wrote:
> Christoph Feck ha scritto:
> > Hello packagers,
> >
> > to minimize disruption caused by the git repo rename, I offered to
> > distribute 19.08.x tarballs with the old name ('kcalcore' instead of
> > 'kcalendarcore').
> >
> > On the other hand, for some packagers that already adjusted it might
> > be convenient to also offer a tarball with its new name.
> >
> > Question:
> >
> > Would it be problematic if the next 19.08.x releases contain both a
> > 'kcalcore' and a 'kcalendarcore' tarball, basically with the same
> > content (except for the directory name)?
>
> If people need the new name, shouldn't they simply use the new Frameworks
> package?
>
> Of course, unless the Frameworks version is not a drop-in replacement
> (Volker?)
It is a drop-in replacement (same library name and ABI), and technically also
with an increasing version number (5.12 to 5.63), unless the 19.08.x version
number was used for the package.
Regards,
Volker
signature.asc
Description: This is a digitally signed message part.
Re: Heads-up: KContacts and KCalendarCore about to move to Frameworks
Christoph Feck ha scritto:
> Hello packagers,
>
> to minimize disruption caused by the git repo rename, I offered to
> distribute 19.08.x tarballs with the old name ('kcalcore' instead of
> 'kcalendarcore').
>
> On the other hand, for some packagers that already adjusted it might
> be convenient to also offer a tarball with its new name.
>
> Question:
>
> Would it be problematic if the next 19.08.x releases contain both a 'kcalcore'
> and a 'kcalendarcore' tarball, basically with the same
> content (except for the directory name)?
If people need the new name, shouldn't they simply use the new Frameworks
package?
Of course, unless the Frameworks version is not a drop-in replacement (Volker?)
Ciao
--
Luigi
Re: Heads-up: KContacts and KCalendarCore about to move to Frameworks
Hello packagers,
to minimize disruption caused by the git repo rename, I offered to
distribute 19.08.x tarballs with the old name ('kcalcore' instead of
'kcalendarcore').
On the other hand, for some packagers that already adjusted it might
be convenient to also offer a tarball with its new name.
Question:
Would it be problematic if the next 19.08.x releases contain both a
'kcalcore' and a 'kcalendarcore' tarball, basically with the same
content (except for the directory name)?
In case of issues, I will only offer a tarball with the old name.
--
Christoph Feck
KDE Release Team
On 09/19/19 18:17, Volker Krause wrote:
On Sunday, 15 September 2019 12:19:14 CEST Volker Krause wrote:
as previously discussed here and finally approved during Akademy we will
move KContacts and KCalendarCore from Applications to Frameworks. This
should hopefully cause minimal disruptions as the versions then released
with KF 5.63 are drop-in replacements for the previously releases with
Applications (same ABI, higher version number).
KCalendarCore will however rename its Git repo in the process to be
consistent (kcalcore -> kcalendarcore). For kdesrc-build users not actively
working on KCalendarCore this should be transparent, otherwise you might
need to adjust the Git remote accordingly.
I'll inform you once this process has been completed.
This has now been executed. Framework releases will start with 5.63.0,
Application releases will end after 19.08.x.
Re: Heads-up: KContacts and KCalendarCore about to move to Frameworks
On Sunday, 15 September 2019 12:19:14 CEST Volker Krause wrote: > Hi, > > as previously discussed here and finally approved during Akademy we will > move KContacts and KCalendarCore from Applications to Frameworks. This > should hopefully cause minimal disruptions as the versions then released > with KF 5.63 are drop-in replacements for the previously releases with > Applications (same ABI, higher version number). > > KCalendarCore will however rename its Git repo in the process to be > consistent (kcalcore -> kcalendarcore). For kdesrc-build users not actively > working on KCalendarCore this should be transparent, otherwise you might > need to adjust the Git remote accordingly. > > I'll inform you once this process has been completed. This has now been executed. Framework releases will start with 5.63.0, Application releases will end after 19.08.x. Regards, Volker signature.asc Description: This is a digitally signed message part.
Heads-up: KContacts and KCalendarCore about to move to Frameworks
Hi, as previously discussed here and finally approved during Akademy we will move KContacts and KCalendarCore from Applications to Frameworks. This should hopefully cause minimal disruptions as the versions then released with KF 5.63 are drop-in replacements for the previously releases with Applications (same ABI, higher version number). KCalendarCore will however rename its Git repo in the process to be consistent (kcalcore -> kcalendarcore). For kdesrc-build users not actively working on KCalendarCore this should be transparent, otherwise you might need to adjust the Git remote accordingly. I'll inform you once this process has been completed. Thanks, Volker signature.asc Description: This is a digitally signed message part.
