Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HELP NEEDED] Prepare Linux binary distrib of Natron 2.6 #990

Open
5 of 7 tasks
devernay opened this issue Jul 23, 2024 · 9 comments
Open
5 of 7 tasks

[HELP NEEDED] Prepare Linux binary distrib of Natron 2.6 #990

devernay opened this issue Jul 23, 2024 · 9 comments
Labels
type:feature New feature or request

Comments

@devernay
Copy link
Member

Make sure to follow our issue report guidelines

Provide a description of your feature request

We should try to release the Qt5-based Natron 2.6.0 anytime soon (see #827 ).
This requires having macOS, Linux and Windows binary distributions. I'm working on the Mac distrib (Intel and Apple Silicon), @acolwell and @rodlie are working on Windows (MINGW64 probably, since MSVC doesn't seem to be ready), but we need help with the Linux builds:

  • Upgrading packages and dependencies from the toolchain (easy, I may even do it as I'm used to it)
  • Packaging with Qt5
  • Installer (or do we only distribute a zip with no installed?)

Is this a realistically implementable feature?

  • My feature is realistically implementable
  • My feature is NOT realistically implementable

Can you contribute in creating this feature?

  • I am unable, or not willing to contribute to creating this feature
  • I am able and willing to contribute to the creation of this feature

Additional details

No response

@devernay devernay added the type:feature New feature or request label Jul 23, 2024
@rodlie
Copy link
Contributor

rodlie commented Jul 23, 2024

I can help with the Qt5 packaging.

Installer (or do we only distribute a zip with no installed?)

We drop the installer and I will provide a "desktop integration" script that copies the desktop/meta/icons where they should be for integrations with launchers and file managers.

@devernay
Copy link
Member Author

Sounds good to me

@bhack
Copy link

bhack commented Aug 13, 2024

Can you verify this bug before the release?
#996

@devernay
Copy link
Member Author

Can you verify this bug before the release? #996

Done. This is not a bug. I updated the doc in NatronGitHub/openfx-io@f547e5f

@Beryesa
Copy link

Beryesa commented Sep 28, 2024

Would you consider taking over the flatpak (as an official distribution)?
It'd be packaged once just like win and mac, and work everywhere.
Distributions can otherwise deal with their native packaging themselves as usual.

@rodlie
Copy link
Contributor

rodlie commented Sep 28, 2024

Would you consider taking over the flatpak (as an official distribution)?

Anyone can maintain that, it's just a simple repack. If the current maintainer of the flatpak can't then someone else will (probably) step up. Official support means one of the devs need to maintain it, that will probably not happen.

It'd be packaged once just like win and mac, and work everywhere.

Our existing Linux builds works everywhere.


Regarding updating the SDK, been busy with other stuff, so I have not done much. Will try to dedicate some time next weekend (I already maintain other SDK's with almost identical depends, so shouldn't take that long).

@Beryesa
Copy link

Beryesa commented Sep 28, 2024

Anyone can maintain that, it's just a simple repack. If the current maintainer of the flatpak can't then someone else will (probably) step up. Official support means one of the devs need to maintain it, that will probably not happen.

I meant as verifying the flatpak if you have interest, but on that topic, it can be directly implemented to the CI process and help with testing as well, which is what they're pushing towards, though the documentation doesn't seem ready yet.

Our existing Linux builds works everywhere.

Sure but some app store integration would be nice, one-click-install shouldn't be underestimated imo (with desktop integration) :D

Regarding updating the SDK, been busy with other stuff, so I have not done much. Will try to dedicate some time next weekend (I already maintain other SDK's with almost identical depends, so shouldn't take that long).

I can help on that part :P
I've quickly put up a PR today, flathub/fr.natron.Natron#39
It works fine in my limited testing but let's see.

@rodlie
Copy link
Contributor

rodlie commented Sep 29, 2024

I meant as verifying the flatpak if you have interest, but on that topic, it can be directly implemented to the CI process and help with testing as well, which is what they're pushing towards, though the documentation doesn't seem ready yet.

Sure, I see no problem with verifying the flatpak. What do we need to do?

I can help on that part :P I've quickly put up a PR today, flathub/fr.natron.Natron#39 It works fine in my limited testing but let's see.

With the SDK part I meant the Linux SDK we use in Natron, it was a general reply to this thread.

Thanks for the PR for the flatpak, sadly none of us (in Natron as far as I know) have admin/write access to the repo, only the maintainer of the flatpak.

@Beryesa
Copy link

Beryesa commented Sep 29, 2024

With the SDK part I meant the Linux SDK we use in Natron, it was a general reply to this thread.

Oh, right, GitHub merged them so I thought you were talking about the Freedesktop SDK 😅

Sure, I see no problem with verifying the flatpak. What do we need to do?

It'd be easy to add a .well-known file but since natron.fr is not in use any more, I think you should contact flathub on matrix or open an issue.

As per https://docs.flathub.org/docs/for-app-authors/verification

I'd like to verify my app that someone else already published

The first step is to gain ownership over your app; see Someone else has put my app on Flathub—what do I do?

I have an existing app but I cannot verify it due to wrong application ID

In most cases, the application needs to be resubmitted with the correct application ID. Please read the application ID requirements carefully and then follow the resubmition guide to resubmit it.

The best approach would be resubmitting for a new ID and authenticate/verify with GitHub, but I'd say let's do it for the 2.6 release like a comeback 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:feature New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants