Distribution and packaging of Saucedacity on other platforms

[generic-pers0n]

Changelog
2022-07-28: Removed Haiku, Slackware, and Alpine. We'll have to look at those another time (Haiku will not be until very later, however).

---

Saucedacity could be packaged and distributed on a numerous amount of platforms. Of course, we focus on 2 main platforms: Windows and Linux. However, it could be a good opportunity to bring Saucedacity to platforms that either 1) need an audio editor or 2) need a modern audio editor (namely being an alternative to Audacity).

Proposed OSes

This list is to be expanded in the mean time, and it might seem surprising (with the way the list is currently):

• Flatpak - We can publish our flatpak to Flathub
• Arch Linux (AUR), as suggested by some.
• Maybe OpenIndiana

Help Wanted

I know that should Saucedacity be working on any platforms on the list above, it'll add to my tasks with Saucedacity, of which I already have enough to do right now. Therefore, I would like to put out a "Help Wanted" sign to anyone who might be interested. If you have experience with packaging, your skills will be especially useful to Saucedacity (and particularly to this issue).

Status

AUR: Researching
Flatpak: Researching. We might be eyeing Tenacity.
OpenIndiana: In progress

Notes on Building

AUR

• Might add some PKGBUILDS.

Flatpak

• Currently eyeing Tenacity's flatpak builds. Comment below if you think this is a good idea.

OpenIndiana

• Building with Conan fails due to Conan executing make -j<n> (e.g. make -j6), which OpenIndiana's make does not like.
  • Building without Conan is currently in the works. I am attempting to find development packages for the different required libraries (right now zlib)

[gotsum]

I hope this is the right place to ask, but have you discovered whether or not the Sauce works on Mint (and with Mint Cinnamon, MATE, and/or Xfce Editions, at that)? I assume so, but want to be sure before switching there from Ubuntu.

[generic-pers0n]

I hope this is the right place to ask, but have you discovered whether or not the Sauce works on Mint (and with Mint Cinnamon, MATE, and/or Xfce Editions, at that)? I assume so, but want to be sure before switching there from Ubuntu.

DE-wise, you should be fine. Distro-wise, I haven't tried Saucedacity on Linux Mint, but it should work without issue. If something tells me otherwise, I'll update you here.

[gotsum]

TY, and likewise if I run into any issues.

[FrostKnight]

I hope this is the right place to ask, but have you discovered whether or not the Sauce works on Mint (and with Mint Cinnamon, MATE, and/or Xfce Editions, at that)? I assume so, but want to be sure before switching there from Ubuntu.

DE-wise, you should be fine. Distro-wise, I haven't tried Saucedacity on Linux Mint, but it should work without issue. If something tells me otherwise, I'll update you here.

Unrelated message, dunno if this will help, but I sent a message to the now almost dead tenacity project in discussions, about how you are a project that they should support...

I hope you will succeed where the other forks trying to overcome audacity, have failed.

On an unrelated note, dunno about the project name, but I very highly recommend you, since unlike the others, you have refused to surrender.

Aka, after a year, you are still working on this.

This is what is needed to break the new owner's grip on the audacity project. Hoping you succeed!

Will try to install at some point, peace yall!

EDIT: Oh almost forgot, saw you were planning to move to QT in the future,

I do have two requests, if possible, can you, make sure you don't add the dbus part of qt, or the webengine part of qt as forced dependencies?

This would make it less likely for a distro I use to adopt your packages and it would unnecessarily bloat your software and make it slower over time.

Not saying, it shouldn't be an option, but I just ask you don't force it.

Again, I thank you for not giving up!

Oh and last thing, the fewer dependencies, the less headache in testing it, there will be, especially if you can build it quicker.

Now I actually will go for now,

My bad...

Have a good one though!

[generic-pers0n]

I hope this is the right place to ask, but have you discovered whether or not the Sauce works on Mint (and with Mint Cinnamon, MATE, and/or Xfce Editions, at that)? I assume so, but want to be sure before switching there from Ubuntu.

DE-wise, you should be fine. Distro-wise, I haven't tried Saucedacity on Linux Mint, but it should work without issue. If something tells me otherwise, I'll update you here.

Unrelated message, dunno if this will help, but I sent a message to the now almost dead tenacity project in discussions, about how you are a project that they should support...

I hope you will succeed where the other forks trying to overcome audacity, have failed.

On an unrelated note, dunno about the project name, but I very highly recommend you, since unlike the others, you have refused to surrender.

Aka, after a year, you are still working on this.

This is what is needed to break the new owner's grip on the audacity project. Hoping you succeed!

Will try to install at some point, peace yall!

EDIT: Oh almost forgot, saw you were planning to move to QT in the future,

I do have two requests, if possible, can you, make sure you don't add the dbus part of qt, or the webengine part of qt as forced dependencies?

This would make it less likely for a distro I use to adopt your packages and it would unnecessarily bloat your software and make it slower over time.

Not saying, it shouldn't be an option, but I just ask you don't force it.

Again, I thank you for not giving up!

Oh and last thing, the fewer dependencies, the less headache in testing it, there will be, especially if you can build it quicker.

Now I actually will go for now,

My bad...

Have a good one though!

Hello! Thanks for the message! I really do appreciate it since I've tried the best I can to keep Saucedacity as it is throughout this entire time. It appears that it's working quite well!

Now, quick thing about the name: the name is a little weird, yes, but...well, I don't know what else to say. It is quite weird XD

Finally, more about my plans for Qt: I don't plan to require the D-Bus part of Qt and WebEngine as dependencies when we switch to Qt for Saucedacity...unless I decide to use D-Bus in Saucedacity >:D (just kidding, I have no plans to use D-Bus at all, don't worry :). As for WebEngine, we shouldn't be needing to use it either, so we shouldn't be having to require that at all (and neither do I want it as a forced dependency). So, TL;DR: I don't plan to require QDBus or WebEngine in Saucedacity any time soon, and I do not plan to force them as dependencies because I also think they make unnecessary bloat.

About your thing about dependencies too: totally agreed. I kind of wish to reduce build time for Saucedacity so it builds faster. I will have to look into this later, but definitely at some point.

Anyways, thanks for stopping by!

[ZeroDot1]

It would be really nice if it is available in Arch Linux (AUR).

[generic-pers0n]

Okay, so I updated our focus for platforms. There are two main distribution platforms prioritized right now:

1. AUR
2. Flatpak

For Flatpak, I'm really taking a look at Tenacity for this. Please comment on this if you guys think this is a good idea.

[TheEvilSkeleton]

Hi, I've previously worked on the Tenacity flatpak. I can write the manifest and (hopefully get it working):

• Add org.tenacityaudio.Tenacity (Audacity fork) flathub/flathub#2444
• https://github.com/tenacityteam/tenacity-flatpak-nightly

[TheEvilSkeleton]

Now, quick thing about the name: the name is a little weird, yes, but...well, I don't know what else to say. It is quite weird XD

About this, perhaps you can try to collaborate with @tenacityteam? I got to know about this project from this Mastodon post: https://fosstodon.org/web/@tenacity/108734780637094669. In that post, there's the following:

We're discussing on how to carry over our work to their project.

Hopefully the name can be carried over or something. Out of respect, Saucedacity is not a good name.

[generic-pers0n]

Hi, I've previously worked on the Tenacity flatpak. I can write the manifest and (hopefully get it working):

* [Add org.tenacityaudio.Tenacity (Audacity fork) flathub/flathub#2444](https://github.com/flathub/flathub/pull/2444)

* https://github.com/tenacityteam/tenacity-flatpak-nightly

First of all, hello and welcome! Second off, sounds good! I do recommend that you test against the latest Saucedacity 1.2 beta 2, so this would likely be another nightly flatpak like Tenacity's flatpak. If you would like to test against Saucedacity 1.1 (our latest stable at the moment) however, that also would work, but Saucedacity 1.2 should be released any moment now, provided I get #20 fixed + everything else (which are mostly minor things).

[generic-pers0n]

Now, quick thing about the name: the name is a little weird, yes, but...well, I don't know what else to say. It is quite weird XD

About this, perhaps you can try to collaborate with @tenacityteam? I got to know about this project from this Mastodon post: https://fosstodon.org/web/@tenacity/108734780637094669. In that post, there's the following:

We're discussing on how to carry over our work to their project.

Hopefully the name can be carried over or something. Out of respect, Saucedacity is not a good name.

Umm...maybe that should be the first priority actually XD. I don't come up with good names, yes, so we should come up with a new name.

However, I am a little concerned that if we carry the name over, we might cause confusion. I'd go for another new name, but I am also not opposed to carrying over the name so long as we don't cause confusion.

[TheEvilSkeleton]

First of all, hello and welcome! Second off, sounds good! I do recommend that you test against the latest Saucedacity 1.2 beta 2, so this would likely be another nightly flatpak like Tenacity's flatpak. If you would like to test against Saucedacity 1.1 (our latest stable at the moment) however, that also would work, but Saucedacity 1.2 should be released any moment now, provided I get #20 fixed + everything else (which are mostly minor things).

Should I submit an MR to Flathub or is there another approach you'd like to take?