https://www.debian.org/doc/manuals/d...c/ch02.en.html
https://www.debian.org/doc/manuals/d...s-and-sponsors
Found this area of stuff, new to me, probably this is it and I was reading old documents. X E.

So to sum up:

1. You claim to be able to program in 'basically anything'
2. You claim to already be able to 'make cross platform stuff'
3. You mention C, Python and Rust specifially.
4. You claim to have 'read about all' you could find on making an application (???)

A "Linux app" is a program...which you claim to be able to code in just about anything; where is the problem, exactly??? You mention how to 'connect in things', but don't bother telling us what you want to connect, how, over what, to what.

Did you try putting "how to create a .deb package on Ubuntu" into any search engine???
https://www.makeuseof.com/create-deb...debian-ubuntu/
https://www.iodigital.com/en/history...u-deb-packages

...because it appears you don't know what a .deb package even IS, nor that you know how to create a program at all. Write whatever program/code you want in whatever language you have a compiler for; can even be as simple as a shell script. Follow the easily-found directions on how to create an installable package, then you can INSTALL IT with the same package manager you already know how to use.

Hard to know how someone 'experienced' with coding in about any language is unclear on what a program is, and that you can't do basic research first (per the LQ Question Guidelines), before posting. Don't appear to have done so, given this post.

Great, it is in Python, I skimmed those docs, anything else I could make a native app with?

Yes I did, I know what a .deb is, I can create cross platform not natively running stuff, basically like an internet browser is, JS is never native. X E.

That documentation you cited does not have anything about actual source code and why do I need to publish my email etc.?

Actually I think I tried to make a snap last time and could not but found Rust was possible to use and now Python is about all I can find for .deb files, should this be deleted because snaps REQUIRE using their store seemingly? Sorry, yes I tried, I failed rather miserably, if anyone knows this stuff please help someone. X E.

Edited original because I found maybe just maybe I could make a not public and not in official snap store snap. .deb seems to be out, all Python, and snaps, is it even possible to have a like private repo snap and own store for snap like I originally asked? Also, I was trying for distribute on like my own app store as a package I can just download to a user's computer from a web server. I would prefer having a merchant of record processing solution so normal snap store is out maybe. I asked zzzcode.ai and it can't figure this out. Anyway, trying for something I could distribute on a custom app store that just downloads it to users with they may install it, can it be done? X E.

Did you read or understand what you were told before???
You *WRITE THE SOURCE CODE*..that is the program you claim to be able to write in just about any language. And if you got that you 'need to' publish your email from anything you read, you didn't read it carefully or didn't understand it. Try again.
Saying "I failed" doesn't tell us anything, so how do you expect anyone to help??? You asked about how to make a .deb package...you were told how, given commands and how-to guides. Either read them and actually DO something, or there isn't a point in asking.
Are you serious???? Did you not bother to read what you were told??? Do you just not pay attention, or are you trolling this site at this point???

AGAIN:

1. Write your program in whatever language you want; you claim to know many, so PICK ONE
2. Follow the directions that (for some reason) had to be looked up for you and spoon-fed to you, on how to make a .deb package

That's it. You somehow think that someone can install a package BEFORE they download it??? That this magical package will somehow show up on their system and when they install it, it will DOWNLOAD ITSELF from your 'custom app store'??? Once you make a .deb package, it contains EVERYTHING it needs to install the software it contains.

Again: it appears you don't know how to write a program, or that you even have an idea of what a program IS, to be honest. You mention rust and python, and seem to ignore the fact that AGAIN (as you were told) you can write this mystery program in any language. And as you've been told numerous times, this "X E."/maybe garbage is plain annoying, and you were asked to stop.

Yes I read all that, I did pay attention, nothing says how to make something in other than Python (.deb). Snaps I cannot find how to keep on my computer and yes they will have to be downloaded, no not from Snap store, own store with a custom payment processor and tax thing. Trying for packaging like I can just download to a user and have them install. X E.

For you just finding this, like my only hope at making a native app as I try for is probably a snap but how to make a local one and distribute as .snap files or what? I hear .snap can be installed as a snap package but how can I keep making one local? X E.

Packaging is tricky, but anything can be packaged. Besides docs of course, for packaging in deb format you may be able to find help in #packaging on oftc.

Lots of people distribute stuff outside of official repositories and app stores. You could host it on a website, or something like github, etc. Lots of github repos provide binary releases, sometimes in a tarball that anyone can use (which is the simplest for you to distribute), and some go to the effort of packaging in various formats, such as deb, rpm, etc. Snap is one format I don't think I've seen people distribute outside of snap store tho.

As an example, check out https://github.com/FreeTubeApp/FreeTube/releases and click on assets - note how many formats they distribute it in, and note deb/rpm/appimage at the bottom.
They likely setup github to automatically build & package for them, as they also provide nightly builds in all those same formats too.

Nice, anyway, I found flatpak is much easier and it has wider support and is "agnostic" when it comes to programming languages. It can still be installed though so close enough to native. Problem solved sort of. Flatpak does require some install steps but hey, native app, solved. X E.

You obviously didn't, and you're lying about it. Because neither of the links you were spoon-fed have ANY mention of Python, and I have no idea what you're going on about with "Python (.deb)". A .deb is like a .rpm...a PACKAGE, containing programs/scripts/files/libraries/whatever-you-want. And **AGAIN**, all of that's explained and well documented.
You don't 'download to a user', and I highly doubt you are going to write anything that anyone would actually pay for, if you cannot follow basic instructions or do a minimum of research. You seem unclear on very basic concepts, and if you want to distribute whatever you write, use a package like .deb or .rpm, and maybe someone will fall for it.
AGAIN: a 'native app' can be written in pretty much any programming language; you claim to be an 'expert' and have the ability to 'program in pretty much anything'. Do you not understand the basic concept of what a program is???

And a snap file can be installed locally...again, do you actually pay attention or do any research??? You want to create a .snap, that starts with you *WRITING A PROGRAM IN ANY LANGUAGE YOU WANT*. Want to distribute?? Then you put it in the snap store; again, don't expect people to keep looking things up for you if you lack the capacity or drive to do it yourself.
https://snapcraft.io/docs/creating-a-snap
https://askubuntu.com/questions/1266...m-a-local-file

And .rpm, .deb, and snap are also 'agnostic' for programming languages...again, it is nothing but a PACKAGE. And it's not 'native', since you then are required to install flatpack (like snap) to get things to work. Any 'install steps' are installing the package.

And AGAIN, as you've been told many times, this "X E." garbage is just plain annoying, and you've been asked to stop by many. And you keep doing it, and somehow expect people here to keep giving you help. That you promptly ignore or don't actually understand.