¡Hola KDE!
El 2017-08-14 a las 14:49 +0200, Maximiliano Curia escribió:
El 2017-08-14 a las 10:40 +0200, Maximiliano Curia escribió:
El 2017-08-06 a las 23:41 +0200, David Faure escribió:
KDE Frameworks 5.37.0 has been uploaded to the usual place.
Thanks for the release, could you also push
¡Hola KDE!
El 2017-08-14 a las 10:40 +0200, Maximiliano Curia escribió:
El 2017-08-06 a las 23:41 +0200, David Faure escribió:
KDE Frameworks 5.37.0 has been uploaded to the usual place.
Thanks for the release, could you also push the tags the v5.37.0 tags
in the git repos?
Thanks, I see
On lundi 14 août 2017 10:40:23 CEST Maximiliano Curia wrote:
> ¡Hola David!
>
> El 2017-08-06 a las 23:41 +0200, David Faure escribió:
> > KDE Frameworks 5.37.0 has been uploaded to the usual place.
>
> Thanks for the release, could you also push the tags the v5.37.0 tags in the
> git repos?
¡Hola David!
El 2017-08-06 a las 23:41 +0200, David Faure escribió:
KDE Frameworks 5.37.0 has been uploaded to the usual place.
Thanks for the release, could you also push the tags the v5.37.0 tags in the
git repos?
Happy hacking,
--
"The most important thing in the programming language is
On samedi 12 août 2017 22:54:51 CEST Andreas Sturmlechner wrote:
> On 10 August 2017 at 23:18, David Faure wrote:
> > Hmm. What's the headache, if the framework name is simply "kirigami2",
> > just
> > like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours
> >
On 10 August 2017 at 23:18, David Faure wrote:
> Hmm. What's the headache, if the framework name is simply "kirigami2", just
> like kcoreaddons is kcoreaddons? Now that my scripts have hacks, yours
> shouldn't need any...
It's a minor inconvenience that repo name and tarball
On jeudi 10 août 2017 21:49:38 CEST Andreas Sturmlechner wrote:
> On Thursday, 10 August 2017 at 21:16, Rik Mills wrote:
> > Indeed it would. For example I have kirigami (v1) and kirigami2 source
> > packages in ubuntu, so human level confusion aside, now renaming
> > kirigami2 tarballs to just
On Thursday, 10 August 2017 at 21:16, Rik Mills wrote:
> Indeed it would. For example I have kirigami (v1) and kirigami2 source
> packages in ubuntu, so human level confusion aside, now renaming
> kirigami2 tarballs to just kirigami is going to give scripting and
> tooling a headache.
Gah, I
Seems good so far. Thank you.
On 10/08/17 20:30, David Faure wrote:
> OK, I don't like having to add hacks to the release scripts, but it looks
> like it's the only way here, short of renaming the git repo.
>
> I fixed the version numbers and repacked kirigami, now as kirigami2.
> Please
On my end looks good.
if you think that renaming the repo is the least ugly way to go, i
would be fine with that
On Thu, Aug 10, 2017 at 9:30 PM, David Faure wrote:
> OK, I don't like having to add hacks to the release scripts, but it looks
> like it's the only way here, short of
OK, I don't like having to add hacks to the release scripts, but it looks like
it's the only way here, short of renaming the git repo.
I fixed the version numbers and repacked kirigami, now as kirigami2.
Please double-check closely that everything is as it should...
kirigami v5.37.0-rc2
Indeed it would. For example I have kirigami (v1) and kirigami2 source
packages in ubuntu, so human level confusion aside, now renaming
kirigami2 tarballs to just kirigami is going to give scripting and
tooling a headache.
On 10/08/17 20:09, Tobias C. Berner wrote:
> Also, given that this was
Also, given that this was previously called kirigami2, and still installs
stuff to .../cmake/KF5Kirigami2/..., .../kirigami.2/... and so
respectively, wouldn't it be less confusing to call this still kirigami2?
mfg Tobias
On 10 August 2017 at 20:52, Andreas Sturmlechner <
On Sunday, 6 August 2017 at 23:41, David Faure wrote:
> KDE Frameworks 5.37.0 has been uploaded to the usual place.
>
> New frameworks: kirigami.
Looks like krigiami still has KF5_VERSION 5.36 and KF5_DEP_VERSION 5.35.0, I
don't think that's intentional?
Regards
14 matches
Mail list logo