Ready to be published? LXer is read by around 350,000 individuals each month, and is an excellent place for you to publish your ideas, thoughts, reviews, complaints, etc. Do you have something to say to the Linux community?
Windows users prefer self-executing application installers, and for the most part, they get the job done well. But those of us on the Linux side of the fence have long since been content with Deb and RPM packages, among other application packaging options.
In the past, I have seen a few different attempts at bringing forth this packaging scheme to the Linux desktop. To say that it has been met with varied success would be kind. But the fact remains that it is the creation of Linux software packaging that needs the most help. I believe the installation of software itself for the end-user is just about where it ought to be. However, are we addressing the packaging needs of the developer? This is open to debate...
My biggest reason for using Debian is the effect of the Debian policies and procedures. When I install a package, it works.
I have no problems with executable extractors, for _local_ things like games and applications that I install as a user. At this moment I have Savage from S2 Games and Google Earth, both installed from self-executing installers, and both in my home directory.
(Savage, sad to say, is the only application which will lock up my system, requiring a power off. Oh well, it was fun to play for a while... I'll get Savage 2 if they ever put out a Linux version)
But testing, vetting, pre-packaging, dependency resolution, are all why I use a _Linux_Distribution_ in the first place.
I have no interest in self-extracting installers for system-wide applications.
I agree. You need some trust in the software source as well. The gpg keys in Debian or derivatives such as Ubuntu are good for that. Finally the way my system is set up if I click on a deb gdebi comes up checks dependencies and if they are in the repo it installs the software (after asking for a root password). If the dependencies are not there that is the fault of the packager....The whole thing is pretty painless when you get used to it. I don't see the need for borking your system with random software installs. It just makes updates a PITA
Post a comment
A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.
Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help
I have no problems with executable extractors, for _local_ things like games and applications that I install as a user. At this moment I have Savage from S2 Games and Google Earth, both installed from self-executing installers, and both in my home directory.
(Savage, sad to say, is the only application which will lock up my system, requiring a power off. Oh well, it was fun to play for a while... I'll get Savage 2 if they ever put out a Linux version)
But testing, vetting, pre-packaging, dependency resolution, are all why I use a _Linux_Distribution_ in the first place.
I have no interest in self-extracting installers for system-wide applications.