Re: ECM metainfo path

2016-04-26 Thread Stephen Kelly
Harald Sitter wrote: > I am actually not sure how we handle this for ECM. CCing Stephen > Kelly who I think is semi-maintaining ECM right now. Hi, Thanks for the heads-up. I'm afraid I'm way out of the loop. I don't know what appstream or /metainfo are. However, let's see if I can contribute.

Re: ECM metainfo path

2016-04-25 Thread Harald Sitter
On Fri, Apr 22, 2016 at 10:13 PM, Matthias Klumpp wrote: > 2016-04-22 12:45 GMT+02:00 Harald Sitter : >> Lost mailing list CC, I am assuming that was intentional? (: > > Oops, no - I didn't see the CC and didn't hit reply-all then... > Adding the list back

Re: ECM metainfo path

2016-04-24 Thread Matthias Klumpp
2016-04-22 12:45 GMT+02:00 Harald Sitter : > Lost mailing list CC, I am assuming that was intentional? (: Oops, no - I didn't see the CC and didn't hit reply-all then... Adding the list back (hope your reply isn't private ;-) ), the mail I sent first is below. > On Thu, Apr 21,

Re: ECM metainfo path

2016-04-21 Thread Luca Beltrame
Il giorno Thu, 21 Apr 2016 12:26:54 +0200 Harald Sitter ha scritto: > doesn't that break compatibility with older appstreams for everything > that uses ECM? if so, I am not sure that is appropriate TBH I noticed that as well (at the same time when we were standardizing the

ECM metainfo path

2016-04-21 Thread Harald Sitter
ahoy ahoy! http://commits.kde.org/extra-cmake-modules/4b7a90bfe7a3e2eb3ae83c946c182a79fabc51e3 doesn't that break compatibility with older appstreams for everything that uses ECM? if so, I am not sure that is appropriate TBH HS ___