On Tue, 2009-07-14 at 11:12 +0530, Kenneth Gonsalves wrote:
On Tuesday 14 Jul 2009 11:05:20 am Krishnakant wrote:
I think he gave the correct advice and you misunderstood him. He probably said something like 'a dedicated postgres user', which meant a special user created by postgres that is dedicated to this particular database. You misunderstood it as 'the dedicated postgres user' which means the user named postgres.
Yes perhaps the wrong words for the right solution. As a side note we indeed were looking at your ticket but did not close it
the one thing you must do is keep a close watch on tickets. Either accept them or reject them immediately. This encourages people to file tickets. They do not expect the ticket to be resolved immediately. They are just happy to know that they are not being ignored. Even rejection as wontfix or not a bug is also acceptable, but do it fast. Also I suggest that all issues you are facing should be filed as tickets. One ticket per issue. And if there is sufficient detail in the ticket you may be surprised to find patches appearing too.
Yes, we will follow this from now. I will forward this to the developers mailing list as well.
as far as deb and rpm is concerned, it is not the job of a developer to make/maintain debs or rpms. If your application is any good, people will come forward to do that. In fact it is a good measure of the acceptability of your app if some one comes forward to package it. I suggest you do not waste your time on this.
True, but people who are not linux experts want to install and test this. They are typicle end users and even after following installation instructions and personal helping over the phone, they find it difficult to install. People seem to be very used to double clicking an executable or at least do every thing in one 1 or 2 commands.
For getting the app tested by non-technical users, I really need to take up the responsibility of making packages. Else what you are suggesting is totally correct.
happy hacking. Krishnakant.