In the process of getting my flatpak up and running, I ran into a face-palm moment when I realised it was building from my local git repository, not the file system.
While testing my GTK/Python GUI, I build and run the flatpak and play around with it. I don’t want to commit broken code, so I’m thinking of having a development manifest that just obtains the source from the local file system and a production manifest that uses my github repository.
I haven’t actually tried this yet, but I’m open to ideas from more experienced folk.
Thanks again,
J.R.
1 Like
OK, figured it out!
Changing this:
"sources" : [
{
"type" : "git",
"url" : "file:///home/jr/Code/leaftracker-gtk"
}
]
To this:
"sources" : [
{
"type" : "dir",
"path" : "/home/jr/Code/leaftracker-gtk"
}
]
Will build and run the flapak from the uncommitted sources. This could indeed be done in the development manifest.
I’m no expert, so I like to keep things simple. I’ve been using the above, but linking to each file individually with
- type: file
path: /home/chris/git/myapp/file?
for each file. Your method of linking to a directory is better, so I’ll use that in future.