Request to Members Making Package Requests

[Eadwine Rose]

Tor is already in MX Package Installer popular packages tab.

[JayM]

Please make package tor

Do you know how I know you didn't read and follow the instructions above in post #1?
1. As Eadwine Rose said, it's already there so you didn't search for it in MX Package Installer.
2. You replied to someone else's old topic with your request instead of starting your own topic here.
3. You didn't include a link to where the package managers could get Tor.
4.

Don't just make abrupt one-line posts like: "Please make package ABC".

[Huckleberry Finn]

"Please make package ABC".

That reminds :

[Spanker-General]

I hope I'm requesting this correctly.

1. UVtools
https://github.com/sn4k3/UVtools
2. Citubox
https://www.chitubox.com/en

[asqwerth]

@Spanker-General

No you're not.

1. post in the appropriate subforum of this package requests board dealing with the MX release you are using. Are you using MX19? MX17/18?

2. make each package request in a separate thread, with the application name in the title of the thread; and

(I'm quoting point 3 of my first post in this thread):
"3. where the package is not so common and isn't something already in the Debian repos, please give a description in your package requests as to what the package you want does/is, and where the source can be found or at least give a web link that provides more info on it. If you want an update of an existing/known package to be in the MX repos, you could just link to some webpage setting out the main bug fixes/new functions.
Don't just make abrupt one-line posts like: "Please make package ABC"."

Caveats:
- providing the source code link is advised. Without source, how are the packagers here supposed to build the package?
- if the code/software is proprietary, the packagers can't package it for our repo and will tell you so
- if the source cannot be packaged to be compatible with the Debian libraries for the MX version you are using (that's why you need to tell us that piece of info), then our packagers will tell you so.

[asqwerth]

[added] OK, it looks like you had posted in the MX19 subforum, just that you tried to combine both package requests into one general thread. Like I said, just give each separate app its own thread and its name in the thread title.

Each app will have to be addressed individually on its own particular set of circumstances.

For instance, my guess is chitubox is proprietary and can't be packaged.

[mbooyzen]

Have a question regarding rapidly developed packages, i have a few that i use appimages for but also gets updated almost monthly. Would this be possible or do I continue using the appimage until it becomes a (slower) package? Currently I use the latest and revert back to previous if I run into an issue.

Then there's a few packages that I build from source as the ones in the repo's are outdated(none in testing/backports) will send them soon.
Thank you

[asqwerth]

Keep in mind:

1. there's a backlog, and the packaging team is doing this in their spare time.
2. so they will probably prioritise what is more important to package for MX (eg security updates, major releases).
3. a monthly request for updated packaging may or may not be deemed important, esp if the updates are just for minor changes. If so, it might be pushed to the back of the queue
4, that is why in your package request it is impt to give more details like changelog, release notes, why this particular update is important, etc. You may want to skip a few updates before making a package request. It looks like appimages are still very much available to you.
5. some updates may not be possible to build/backport on Buster base, or may take longer as it's more difficult. If so, appimages might still be better for your use case.
6. be patient.

[Stevo]

Some packages we depend upon Debian to build upstream, and then we can rebuild them for MX.

Some rapidly developed programs are quick and trivial to update, while others take a lot of time and effort.

[mbooyzen]

Okay, thanks for that. In that case i'd stick to AppImages for those. I have no idea how you do this, so thought i ask first. Thanks alot