Re: [Firebird-docs] Comment out empty images dir in build.xml?

[Tilo M. <tm...@al...>]

Hi Paul,

"Paul Vinkenoog" <pa...@vi...> schrieb im Newsbeitrag
news:Pin...@s4......
> Hi Tilo,
>
> > [ about the empty folder src\docs\firebirddocs\images: ]
>
> > Let's comment it out then, and uncomment it as soon as something is
> > placed in that folder. And when it is no longer empty, it will also
> > no longer be pruned by "update -P", so that part of the problem will
> > solve itself.
>
> Meanwhile I've thought of something that may be better:
>
> - create a file Readme.txt in the images dir;
> - change the lines in the *html targets in build.xml that now read:
>     <fileset dir="${src.dir}/docs/firebirddocs/images"/>
>   to:
>     <fileset dir="${src.dir}/docs/firebirddocs/images"
>                                           excludes="Readme.txt"/>
>
> The first step will prevent the local dir to be deleted by update -P.
> The second step will prevent Readme.txt to be copied to the dist tree.
>
> The advantage is that we won't have to change build.xml back and
> forth; this solution will work whether image is "empty" (but for
> Readme.txt) or not.
>
> Readme.txt must contain a few lines to explain why it is there and
> why it shouldn't be deleted. I call it Readme.txt instead of e.g.
> Dummy.txt because this makes it more likely that someone will read
> the contents before he decides to delete it.
>
> What do you think?

Go for that workaround, later when the first image is used in the docs we
can rollback that change.

> Greetings,
> Paul Vinkenoog

--
Regards,
Tilo Muetze
--
Marathon - The SQL Tool for Firebird & InterBase
http://gmarathon.sourceforge.net