perhaps the GUI should include a dialogue on first startup regarding storing the blockchain in a custom location

selsta: hello. I'm now trying to make so that the appdata always has an actual release date. github.com/BigmenPixel0/monero-gui/…blob/flatpak/flatpak/CMakeLists.txt... (full message at <libera.ems.host/_matrix/media/v3/do…5b6c901a95651aa92d0fd53c6b02218c511>)

s/an/a/, s/error/mistake/

this will set the release date to when we touched the cmakelists / last git commit, this can be up to a week earlier than the actual release date

setting it to when CI is running would make more sense to me

selsta: But there is also another method with git.

Something wrong in it?

Oops, I understand now.

yes, it won't match with the actual release date since time between last tag and the actual release date can differ by up to a week

selsta: So is it possible to use `date` command there?

I would do it similarly to this

Add a `<dstamp>` placeholder

and then run `sed -rf s/<dstamp>/$(date '+%Y%m%d')/g` from CI

And what about $(date '+%Y-%m-%d')?

I don't fully understand how should it work. Get the current date (when CI is working) or timestamp of some file?

<selsta> "Add a `<dstamp>` placeholder" <- Where?

inside the date thing

then you run the sed command so that it replaces <dstamp> with the real date

this is assuming you want to only show the latest version

<selsta> "then you run the sed command..." <- That looks good, without env.

the command i posted was only an example, you will have to adapt it

<selsta> "the command i posted was only an..." <- This works:... (full message at <libera.ems.host/_matrix/media/v3/do…da7ea8b0c8098a555906b5d81f1af1cebfd>)

I meant without CMake at all

So now it's need to select a "trigger" for cmake subdirectory. Is existing of #FLATPAK_ID good?

selsta: Sorry, I needed to say it.

s/#FLATPAK_ID/$FLATPAK\_ID/

I wouldn't use CMake for this and just run sed from here monero-project/monero-gui #4151/files#diff-0204cdf2cea745a516b9aa6ee61205f02d0738627a1ae7a74c7800865c3a8115R22

selsta: Also it will need to get the version there.

* it will be need to

${{ github.event.release.tag_name }}

can also be done from github actions without CMake

selsta: Good, I will do so.

so after each `uses: actions/checkout@v3` I would run 2 sed commands, one that replaces with the current date and one that adds `${{ github.event.release.tag_name }}`

you have a version placeholder and a date placeholder

<selsta> "you have a version placeholder..." <- ```... (full message at <libera.ems.host/_matrix/media/v3/do…8e1a2fc9c2e84769c6bb580a214c54729b5>)

Oops, wait.

the version is wrong

sed -i 's/<version>/${{ github.event.release.tag_name }}/g' file

selsta: ```

sed -i 's/<version>/'"${{ github.event.release.tag_name }}"'/g'

```

- name: Add version and date

run: |

sed -i 's/<version>/${{ github.event.release.tag_name }}/g' monero-gui/flatpak/org.getmonero.Monero.metainfo.xml

sed -i 's/<date>/'"$(date '+%F')"'/g' monero-gui/flatpak/org.getmonero.Monero.metainfo.xml

flatpak directory won't be.

* flatpak directory won't be in the final.

looks good assuming the path is correct

and you have to add this after each checkout

<selsta> "and you have to add this after..." <- Maybe only after the latest?

Prt 3

* Part 3

I don't know when it uses these .xml files

Because the appdata will install there.

then adding it in part3 should be enough

selsta: Ok.

So are there any problems also? I will need to add checkers and everything is fine..?

can you clarify? problems where?

selsta: Problems to push

you can update the PR

selsta: Well, I will update when it works. I'm now at the `flatpak` branch for testing.