I get your point, I just don't agree with it. It is often easier to just
install plone than it is to:
1. search and discover LocalFS
2. decide if it is too old or if it can be satisfactorily patched.
3. patch it (thank you Robert)
4. test, test and test it.
5. Hope that it still works in the next version of zope that comes out.
6. plan to test, test and test it in the next version of zope. And the next,
and on and on.
Or you can install plone and know that it has been well tested, it is well
maintained and has a large community. One click and you are done. The next
version of plone will also be well tested.
Look, you can do it anyway you want but if you want to imply that my
suggestion to use Plone is 'insane' you need to come up with a better
alternative than LocalFS.
But of course this is all moot. For most installs the best way to use large
On Sat, Mar 28, 2009 at 1:15 AM, Jens Vagelpohl <j...@dataflake.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Mar 28, 2009, at 01:16 , thedag...@gmail.com wrote:
> >> Telling someone to install all of Plone just to make filesystem
> >> content available seems insane, sorry. There are several products out
> >> there which can do the job, like LocalFS.
> > LocalFS has been updated since 2006. There is nothing in the zope
> > world that is as well maintained as plone. Sorry.
> You're not getting my point. Why would I install a huge package just
> for one small functionality?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (Darwin)
> -----END PGP SIGNATURE-----
> Zope maillist - Zope@zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -