#asahi-dev · 2023-04-02 14:47
orowith2oswhat does asahi/mesa link against?#asahi-dev · 2023-04-02 14:47
orowith2osnot without risking ABI breakage#asahi-dev · 2023-04-02 14:47
orowith2os21.08 and 22.08#asahi-dev · 2023-04-02 14:47
orowith2osonly the currently supported ones#asahi-dev · 2023-04-02 14:47
orowith2oskeep in mind you'll have to build the flatpak for every branch of the freedesktop runtime#asahi-dev · 2023-04-02 14:46
orowith2osit's allowed to just neglect it#asahi-dev · 2023-04-02 14:46
orowith2osyou don't strictly have to have the metadata outside of flathub#asahi-dev · 2023-04-02 14:46
orowith2osthere are other source types, namely `dir`#asahi-dev · 2023-04-02 14:45
orowith2osyou see the current sources, where it has a git url, checksums, etc?#asahi-dev · 2023-04-02 14:45
orowith2osyeah, whatever the PKGBUILD uses, the flatpak will too#asahi-dev · 2023-04-02 14:45
orowith2osbut what you *can* do is clone asahi/mesa to the normal PKGBUILD clone directories and point the flatpak towards the local directory#asahi-dev · 2023-04-02 14:44
orowith2osYou can't take in variables from outside the build env, no#asahi-dev · 2023-04-02 14:43
orowith2osfrom there it's moving files around#asahi-dev · 2023-04-02 14:43
orowith2ospoint the flatpak manifest toward the git repo that the PKGBUILD clones and whenever you build the PKGBUILD, it'll update the flatpak too#asahi-dev · 2023-04-02 14:43
orowith2osyeah, that can be done#asahi-dev · 2023-04-02 14:42
orowith2osOH#asahi-dev · 2023-04-02 14:42
orowith2osit's easier when I have something to base off of#asahi-dev · 2023-04-02 14:41
orowith2osI'm probably misunderstanding#asahi-dev · 2023-04-02 14:41
orowith2osIf it searches often enough, or has a webhook trigger, the flatpak will update whenever the PKGBUILD is#asahi-dev · 2023-04-02 14:41
orowith2osThat's that the x-checker-data does, though?#asahi-dev · 2023-04-02 14:40
orowith2osIs there a way to trigger a workflow from another git repository?#asahi-dev · 2023-04-02 14:39
orowith2osYou can build the Flatpak by running a command like this: `flatpak-builder --user --install --force-clean build-dir org.irssi.irssi.yaml`#asahi-dev · 2023-04-02 14:39
orowith2oswant me to get on that?#asahi-dev · 2023-04-02 14:38
orowith2osjust make the update workflow check a dev branch, and change the URL it searches#asahi-dev · 2023-04-02 14:38
orowith2osoh yeah this is doable#asahi-dev · 2023-04-02 14:37
orowith2osif you have a dev PKGBUILD I can base a workflow off of, that would work just fine. Or, if everything's local, point toward a specific source URL for Mesa#asahi-dev · 2023-04-02 14:36
orowith2osWe can make a separate branch for dev#asahi-dev · 2023-04-02 14:36
orowith2osyou can also build it manually if desired#asahi-dev · 2023-04-02 14:35
orowith2oswhen a commit is pushed, namely a mesa update, it'll build for you#asahi-dev · 2023-04-02 14:35
orowith2oswhat I've been having trouble with is generating usable archives from the workflows#asahi-dev · 2023-04-02 14:34
orowith2osthe local workflows here do that too, on a similar schedule#asahi-dev · 2023-04-02 14:34
orowith2osFlathub has a bot go through all packages it hosts and updates them using that mechanism#asahi-dev · 2023-04-02 14:34
orowith2osyep#asahi-dev · 2023-04-02 14:33
orowith2osso long as it knows what to check for, it'll keep in sync with that#asahi-dev · 2023-04-02 14:33
orowith2ossee the diff here: https://github.com/orowith2os/mesa-asahi-flatpak/commit/71dc18316a2127cfeee36fc5848fc75d3733261c#asahi-dev · 2023-04-02 14:33
orowith2osthe workflows#asahi-dev · 2023-04-02 14:32
orowith2osit updates those too#asahi-dev · 2023-04-02 14:32
orowith2osmarcan: it'll update for you, all you need to do is update the PKGBUILD#asahi-dev · 2023-04-02 14:31
orowith2oswant to make a repo on the AsahiLinux org and push the current repo there?#asahi-dev · 2023-04-02 14:31
orowith2osmmmm, I'd rather have the flatpak manifest in its own repo, for my own sanity#asahi-dev · 2023-04-02 14:30
orowith2osToss me some aarch64 runners for github, generate an archive, and the pacman package extracts and moves around those binaries?#asahi-dev · 2023-04-02 14:29
orowith2oshow do you want to handle builds?#asahi-dev · 2023-04-02 14:29
orowith2osMakes sense#asahi-dev · 2023-04-02 14:28
orowith2osI think that's doable#asahi-dev · 2023-04-02 14:28
orowith2osyou mean building it inside of Flatpak, as intended, and shipping those binaries through the native package manager?#asahi-dev · 2023-04-02 14:28
orowith2osI thought you still meant building the driver on the host and mounting it in inside of Flatpak#asahi-dev · 2023-04-02 14:28
orowith2ossorry#asahi-dev · 2023-04-02 14:28
orowith2oswait, still misunderstood#asahi-dev · 2023-04-02 14:27
orowith2osIf you are a distro packager I do believe it makes sense to start making a nvidia package for the Flatpak extension especially for beta versions. This should probably not be used to package host versions of Mesa though because they link to host libraries outside of libc. #asahi-dev · 2023-04-02 14:27
orowith2osI'd like to make a quote from the article: