Do you want people to use Cherokee or not ?!?
Wake me up when the answer is, "..we want people to use Cherokee...".
Open Source or not, if I cannot use the software it is useless to me.
Ray C. Horn
CONFIDENTIALITY NOTICE: This email is CONFIDENTIAL and intended only for those
to whom this email has been sent by the original sender. You may
purchase the rights to redistribute this email by clicking here.
From: [email protected]
Date: Mon, 31 Aug 2009 15:47:32 -0300
Subject: Re: [Cherokee] Cannot start Cherokee 0.99.23
To: [email protected]
CC: [email protected]; [email protected]; [email protected]
Come on Ray. Don't forget about Cherokee is open source software... There is no
guarantee to upgrade and get it working like a charm. Try to be nice. This is
not Cherokee's or Alvaro's fault. This is just something that may happen.
Please accept my apologies in advance if I'm taking your opinion in a wrong way.
Pablo
On Mon, Aug 31, 2009 at 3:39 PM, ray horn <[email protected]> wrote:
Failure to go after an upgrade is worse than broken config, IMHO.
On the other hand, a broken config can be fixed by comparing the original
config with the config after the upgrade but in my case Cherokee 0.99.23 is
simply non-functional - end of story.
Ray C. Horn
CONFIDENTIALITY NOTICE: This email is CONFIDENTIAL and intended only for those
to whom this email has been sent by the original sender. You may
purchase the rights to redistribute this email by clicking here.
From: [email protected]
Date: Mon, 31 Aug 2009 11:28:09 -0700
Subject: Re: [Cherokee] Cannot start Cherokee 0.99.23
To: [email protected]
CC: [email protected]; [email protected]; [email protected]
On Sat, Aug 29, 2009 at 2:13 PM, Leonel Nunez <[email protected]> wrote:
And this is what the PPA and Debian Unstable is meant for. see what we can
fix before it enters on the next stable release. That's why I always ask
to backup your cherokee.conf before upgrading so we can go back to the
version we got working.
and this is something we must fix in the cherokee package by
1 editing the cherokee.conf
or
2 display a message with this change.
With Arch packages, we can add a post-upgrade hook to display messages about
things that changed that the user should be aware of. Is there something
similar for apt?
I think that automatically editing the user's config file is a Bad Idea,
because, honestly, that their own file to deal with. Give them a message of
important changes (or even just a "make sure to read the changelog, available
at [url]") is much better, because it prevents problems such as these without
taking away control. Forgive me if I misunderstand, but the recent versions of
cherokee are only packaged for Sid (unstable), right? It's my thought that
anyone who uses Sid should be prepared to invest time to fix things when
upgrading software. I know that I never update my Arch machines if I don't
have time to fix any issues that may crop up as a result, and I've accepted
that as the price for having the bleeding-edge.
--
James Pearson
--
The best way to predict the future is to invent it.
- Alan Kay
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
_______________________________________________
Cherokee mailing list
[email protected]
http://lists.octality.com/listinfo/cherokee
