Ignore .svn directories on export

On Sun, 23 Sep 2007 18:37:43 +0200
"Arieh Skliarouk" <skliariehgmail.com> wrote:

> On my website I am using SVN tool to track changes.
> 
> When I am doing static export of the website, meshcms
exports
> all .svn/* files as well. IMHO, these should be ignored
on the export
> stage, as well as CVS directory.

At the moment, static export copies everything, there are no
filters
configured.

> BTW, are there any plans to integrate versions tracking
support into
> meshcms?

There are plans to add a save-without-publishing feature,
but not to
support SVN or other VCS products.

Luciano


------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MeshCMS-Discussion mailing list
MeshCMS-Discussionlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesh
cms-discussion

> BTW, are there any plans to integrate versions tracking
support into 
> meshcms?
Yes there are plans around, but they depend on the Commons
Virtual File System Apache project:
http://commons.apache.
org/vfs/
and especially it's support for VCS as a FS implementation.
At the moment
there are only in sandbox some trials and not a default
out-of-the-box
solution.

MeshCMS is a "File based CMS", so changing it's
implementation from a
*real* FS to a Virtual FS is possible if:
1.- there's support for the required mapping from real FS to
VFS (i.e. all important operations are 
supported).
2.- the LocalFiles (the equivalent of the real FS)
implementation in VFS should be fast enough (so 
that installations who don't use VCS or other similar
solutions not to pay a too high performance 
overhead for an unused feature)
3.- a VCS implementation (SVN in this case) that works and
is default supported.

#2 and #3 are unfortunately not solved yet :( : at the
moment the "stable" VFS implementation
for local files is very slow and has memory leaks too, and
the VCS support is only in the sandbox,
it's incomplete and very hard to start something with it
:(.

To solve #2 allot of lobby is required on the Apache lists
as IMHO it's the duty of the authors
to solve the performance problem. Community may help but
profiling a FS it's not easy.

To solve #3, community code contribution and votes/lobby are
required, as the authors don't
seem to feel responsible for this area, but they would be
more than happy to include a "working" 
contribution.

As soon as #2 and #3 are solved I can release the support
for MeshCMS.

Ahmed.


------------------------------------------------------------
-------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MeshCMS-Discussion mailing list
MeshCMS-Discussionlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesh
cms-discussion