For Services, Apps, and Daemon, it should be OBLIGED to provide EASY configurater!!
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Installers are existing for tvtime, xorg, mailing services, ...
Quote:
From now on packages that are coming under testing and Debian survey for becoming one day in Stable, this without any installer, will be simply rejected. The default values, with queries for machine specific values, will be set to fully enable a running service or application within the installer.
This rule was intended to giving a considerable chance of using Linux to everyone. With performing the last coding step of your application, we do appreciate your understanding.
dpkg --configure
What about this ? Cool idea?
I mean we do NOT need googling 20 hours to install something (n00b) or use Linux 20y. I mean look this planet how it works. The more complicated it is the less chance it has to be implemented. So please follow this rule and review all the packages. Put them to testing if they do not follow this rule. We have many many thousand .
Do something, well, Debian will do nothing ... like we can expect.
Last edited by frenchn00b; 09-10-2009 at 10:53 AM.
The problem with FOSS is it's mostly a volunteer effort. Sure you can tell package maintainers how you expect it to be done but they can then tell you they don't have time and they'll focus their efforts elsewhere.
I'm all for painless installs but if a distro wants to make it painless then its own volunteers are likely to be the ones that need to put in the extra effort.
What is more likely to happen as a result of this than getting clean installs will be you'll end up having to do a web search for whatever it is you want then go and build your own package or find one in a different repository. On RedHat there are occasionally things I want that I have to go find elsewhere because they're not in RedHat's on repositories.
The problem with FOSS is it's mostly a volunteer effort. Sure you can tell package maintainers how you expect it to be done but they can then tell you they don't have time and they'll focus their efforts elsewhere.
I'm all for painless installs but if a distro wants to make it painless then its own volunteers are likely to be the ones that need to put in the extra effort.
What is more likely to happen as a result of this than getting clean installs will be you'll end up having to do a web search for whatever it is you want then go and build your own package or find one in a different repository. On RedHat there are occasionally things I want that I have to go find elsewhere because they're not in RedHat's on repositories.
Well.... actually personaly, when I code, I never do howto and if you ask me how it works after one year, I havent any single idea. I relook the code and after min or some time, I find out.
I mean that s a normal tendency of a coder... after efforts , hassles, ... he wants to pass to something else. So tiring when its a hard code.
so he leaves it like this. No completion or finition. That s a natural tendency, and man, all on this planet is made like this. Nobody really cares, others, and time consuming to figure out how the tricks are to get it work. But luckily there is good developments, luckily.
Well.... actually personaly, when I code, I never do howto and if you ask me how it works after one year, I havent any single idea. I relook the code and after min or some time, I find out.
I mean that s a normal tendency of a coder... after efforts , hassles, ... he wants to pass to something else. So tiring when its a hard code.
so he leaves it like this. No completion or finition. That s a natural tendency, and man, all on this planet is made like this. Nobody really cares, others, and time consuming to figure out how the tricks are to get it work. But luckily there is good developments, luckily.
LOL -- pretty much sums it up for many of us, I think, unfortunately.
I'm really bad for making some code, or a program, or working on some pre-existing thing and adding to it, and once it's getting out of control in terms of manageability, I decide I should add some "help" documentation to it. This usually ends up being some sort of built-in help page or help-function, rather than a .txt document or a README file, and because I tend to be obsessive & picky, AND long winded at times, my help-function eventually becomes as unmanageable as the rest of the program
Anyhow, on the original topic of this thread: While I agree it's nice to have a simple, convenient way of installing something, it isn't necessarily easy to make that method transparent across distros, versions, or whatever. And, I feel that the statement quoted in the OP's original post, implies that basically, as a result, a lot of otherwise great software might be tossed to the wayside, simply because some 'panel' of 'suits' decides that the installation method isn't up to par.
I don't know about "most" people, but I don't mind a challenge sometimes (or a lot of the time, really) when trying to get something installed that isn't intended to be installed the way I want to install it. Maybe that's why I'm still Slacking -- I like that down-to-earth hacking, configuring type of stuff. Perhaps Debian users don't like hacking & fiddling?? I've never tried a Debian, so..
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.