[Suggestion] Publish to Flathub #1572

Closed
opened 2023-07-09 07:55:22 +00:00 by RaptaG · 30 comments

Flathub is "the Linux app store" which includes a lot of applications available on Linux. The current installation methods might be good, but Flathub is popular, intergrated within most package managers and make distributing an app on all Linux distros easy!

Flathub is "the Linux app store" which includes a lot of applications available on Linux. The current installation methods might be good, but Flathub is popular, intergrated within most package managers and make distributing an app on all Linux distros easy!
Owner

You mean publishing the api? Or the frontend and api? Or the desktop app only?

I guess if we do flatpack, we also need to do snap.

You mean publishing the api? Or the frontend and api? Or the desktop app only? I guess if we do flatpack, we also need to do snap.
Author

You mean publishing the api? Or the frontend and api? Or the desktop app only?

I guess if we do flatpack, we also need to do snap.

Yeah I meant the desktop app

> You mean publishing the api? Or the frontend and api? Or the desktop app only? > > I guess if we do flatpack, we also need to do snap. Yeah I meant the desktop app
Owner

want to send a PR?

want to send a PR?
konrad reopened this issue 2023-07-10 10:36:38 +00:00
Author

want to send a PR?

I never published an app to Flathub, I will try though :P

> want to send a PR? I never published an app to Flathub, I will try though :P
Author

I'll do it now

I'll do it now
Author

Do you want me to create the .yml action or publish it myself there?

Do you want me to create the `.yml` action or publish it myself there?
Author

I'm no programmer (just yet), know the basics, but it confusing I don't think I'll be able to do it. I'll keep trying though

I'm no programmer (just yet), know the basics, but it confusing I don't think I'll be able to do it. I'll keep trying though
Owner

Electron Builder (that's the tool we're using to build the desktop app) has a section about Flatpack which we could build upon.

It should be published via the CI, not uploaded manually.

Electron Builder (that's the tool we're using to build the desktop app) [has a section about Flatpack](https://www.electron.build/configuration/flatpak) which we could build upon. It should be published via the CI, not uploaded manually.
Owner
There's also this: https://github.com/go-vikunja/desktop/issues/7
Author

It should be published via the CI, not uploaded manually.

Yes I agree

https://github.com/go-vikunja/desktop/issues/7

I could fork and improve that yeah

> It should be published via the CI, not uploaded manually. Yes I agree > https://github.com/go-vikunja/desktop/issues/7 I could fork and improve that yeah
Author

This happened: https://github.com/go-vikunja/desktop/issues/7#issuecomment-1629070960

Hello @lpyparmentier! I'm trying to clone your repository (git clone ssh://git@gitlab.parmentier.io:24/lparmentier/flatpak-vikunja.git) but I get this:

Cloning into 'flatpak-vikunja'...
git@gitlab.parmentier.io: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

What should I do?


I downloaded it as .tar.gz.

This happened: https://github.com/go-vikunja/desktop/issues/7#issuecomment-1629070960 > Hello @lpyparmentier! I'm trying to clone your repository (`git clone ssh://git@gitlab.parmentier.io:24/lparmentier/flatpak-vikunja.git`) but I get this: > > ``` > Cloning into 'flatpak-vikunja'... > git@gitlab.parmentier.io: Permission denied (publickey). > fatal: Could not read from remote repository. > > Please make sure you have the correct access rights > and the repository exists. > ``` > > What should I do? --- I downloaded it as `.tar.gz`.
Author

Vikunja desktop is available only for x86_64 architectures right?

Vikunja desktop is available only for x86_64 architectures right?
Author

How should I name the package: dev.kolaente.Vikunja or io.vikunja.Desktop or something else?

Edit: I kept the second one

How should I name the package: `dev.kolaente.Vikunja` or `io.vikunja.Desktop` or something else? Edit: I kept the second one
Owner

How should I name the package: dev.kolaente.Vikunja or io.vikunja.Desktop or something else?

Edit: I kept the second one

Yeah the second one is great.

Vikunja desktop is available only for x86_64 architectures right?

Yes.

> How should I name the package: `dev.kolaente.Vikunja` or `io.vikunja.Desktop` or something else? > > Edit: I kept the second one Yeah the second one is great. > Vikunja desktop is available only for x86_64 architectures right? Yes.
Author

I am almost done @konrad

I am almost done @konrad
Author
@konrad here is my progress so far https://codeberg.org/RaptaG/vikunja-flathub-prepare
Author

If you wanna change anything, make sure to PR it!

If you wanna change anything, make sure to PR it!
Author

You'll have to write a comment here saying you are giving me permission to PR this myself to Flathub too.

Actually, do you want to PR this yourself?

You'll have to write a comment here saying you are giving me permission to PR this myself to Flathub too. Actually, do you want to PR this yourself?
Owner

Looks great! Can you PR this to https://kolaente.dev/vikunja/desktop?

Looks great! Can you PR this to https://kolaente.dev/vikunja/desktop?
Owner

I'll look into how we can get this on flathub

I'll look into how we can get this on flathub
Owner

okay, looks like this is only submitting a PR to their repo with the manifest? I thought we'd need to push a built Flatpack image to their site or something.

I'll do a PR on Flathub.

okay, looks like this is only submitting a PR to their repo with the manifest? I thought we'd need to push a built Flatpack image to their site or something. I'll do a PR on Flathub.
Author

Ping me there if you want(on the Flathub PR)

Ping me there if you want(on the Flathub PR)
Author

Now I need to make the .yml which will update the version and hash automatically, right? Or will you do it manually with each release?

Now I need to make the `.yml` which will update the version and hash automatically, right? Or will you do it manually with each release?
Owner
PR is up: https://github.com/flathub/flathub/pull/4319
Author

I approved the changes

I approved the changes
Owner

Now I need to make the .yml which will update the version and hash automatically, right? Or will you do it manually with each release?

You mean the CI config? Not quite sure how to automate that, but afaik it's only a push to a git repo? That should go into the CI, yes.

Let's wait until we have the git repo.

> Now I need to make the .yml which will update the version and hash automatically, right? Or will you do it manually with each release? You mean the CI config? Not quite sure how to automate that, but afaik it's only a push to a git repo? That should go into the CI, yes. Let's wait until we have the git repo.
Author

Now I need to make the .yml which will update the version and hash automatically, right? Or will you do it manually with each release?

@konrad?

> Now I need to make the `.yml` which will update the version and hash automatically, right? Or will you do it manually with each release? @konrad?
Owner

Do you want to continue the Flathub PR? Looks like there's more work to be done and I don't really know anything about Flatpack.

Do you want to continue the Flathub PR? Looks like there's more work to be done and I don't really know anything about Flatpack.
Owner

Now I need to make the .yml which will update the version and hash automatically, right? Or will you do it manually with each release?

@konrad?

Let's wait for the git repo from flathub.

> > Now I need to make the `.yml` which will update the version and hash automatically, right? Or will you do it manually with each release? > > @konrad? Let's wait for the git repo from flathub.
Author

Vikunja is now on Flathub (quite some time for that matter), so this can be closed

Vikunja is now on Flathub (quite some time for that matter), so this can be closed
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#1572
No description provided.