https://bugs.kde.org/show_bug.cgi?id=395893
--- Comment #3 from Harald Sitter <sit...@kde.org> --- I feel like I discussed this somewhere already? Bunch of problems: a) how to find appdata files? in general we can search *appdata.xml BUT what if the source configures the file through cmake? (I do remember at least 3 repos where I have seen that) b) what's the date? date of tar creation? date of tag? date of actual public release? c) tarme should be readonly on the repo as it does, or at least did, get used by some distros to generate snapshot tarballs (FTR: doesn't affect neon since neon doesn't go through tarme) The largest problem to me is that KDE does releases in such a messy way. Where any amount of time may pass between the release process beginning and it actually getting announced to the public. In practice the release git tag should present the state of the source as it is in-tar. For that to be true, releaseme would have to inject the release data into the appstream file before creating the tar. Essentially before the current functionality of tarme runs. The trouble is that N days may pass between that time (which is where the data would get generated) and running tagme, so the date that was injected may be wrong. And then there is also the design problem that tarme should not be pushing to the repo. That could conceivably be solved by having a separate command to inject the release metadata (IOW one runs appdatame -> tarme -> tagme). I am not convinced that is all to nice but meh. -- You are receiving this mail because: You are watching all bug changes.
