I'm with Bruce here!
Charley
Bruce Hohl wrote:
> A practical word from a user:
>
> I (a user) don't generally care if it takes an hour to
> install an accounting package that I will later spend
> untold hours with. I do care if I can not even
> install it at all for lack of instructions. And,
A practical word from a user:
I (a user) don't generally care if it takes an hour to
install an accounting package that I will later spend
untold hours with. I do care if I can not even
install it at all for lack of instructions. And, I
also care deeply about the functionality provided.
So just
Mads,
Agreed on the general ideas.
The only issue at the moment is that I think it would require a lot of
rewriting of a lot of code (introducing more errors and delays when we
are looking at re-engineering anyway). I think that the way to go
about this is to come up with an idea of where we wan
Chris Travers wrote, On 12/13/2006 10:51 PM:
> I favor the idea of a post-install configure script. Obviously we
> don't want it in the web directory :-)
>
Now you mention it: Couldn't/shouldn't all CGI entry points be moved to
a cgi-bin folder and apache be configured to execute cgi in that
ningham <[EMAIL PROTECTED]>
Subject: Re: [Ledger-smb-devel] Debian packages and Bruce Hohl Install
To: ledger-smb-devel@lists.sourceforge.net
On Wed, Dec 13, 2006 at 11:15:10AM -0800, Chris Travers wrote:
> in the RPM's the fear is that if these are ever included in a
> repository that m
Chris Travers writes:
> in the RPM's the fear is that if these are ever included in a repository
> that might be used during installation, we can;t guarantee that
> PostgreSQL is running at the time of installation.
In a Debian package we should then fall back to an alternative such as a
high-prio
Hugh;
I favor the idea of a post-install configure script. Obviously we
don't want it in the web directory :-)
Best wishes,
Chris Travers
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay
On Wed, Dec 13, 2006 at 11:15:10AM -0800, Chris Travers wrote:
> in the RPM's the fear is that if these are ever included in a
> repository that might be used during installation, we can;t guarantee
> that PostgreSQL is running at the time of installation. I suppose
> that we could try to start Po
Hi John and others;
Two comments relating to how things might get more interesting if
included in the initial OS install:
in the RPM's the fear is that if these are ever included in a
repository that might be used during installation, we can;t guarantee
that PostgreSQL is running at the time of i
Chris Travers wrote:
> Currently the thinking is that we don't want to set the system up with
> default passwords which would allow anyone a window into accessing the
> applicaiton remotely. Making it "just work" on installation is
> unfortunately at odds with that idea.
On Linux that problem is
Chris Travers wrote:
> Hi David;
>
> Currently the thinking is that we don't want to set the system up with
> default passwords which would allow anyone a window into accessing the
> applicaiton remotely. Making it "just work" on installation is
> unfortunately at odds with that idea.
>
> I thin
Hi David;
Currently the thinking is that we don't want to set the system up with
default passwords which would allow anyone a window into accessing the
applicaiton remotely. Making it "just work" on installation is
unfortunately at odds with that idea.
I think we might be able to do something li
On Fri, 2006-12-01 at 09:05 -0500, Seneca Cunningham wrote:
> On Fri, Dec 01, 2006 at 08:55:04AM -0500, Michael Schultheiss wrote:
> > Seneca Cunningham wrote:
> > > Hi, I'm the LedgerSMB developer who made the packages. The current
> > > packaging is currently a bit on the crude side ...
On Thu,
13 matches
Mail list logo
