Hi Torsten!
Sorry that I was not able to reply earlier.
The workaround that you have found works,
but there is also another way (which is supposed
to be 'straight'). I think that these things are
explained in the documentation, but maybe they
are not so clear.
The Subversion for the books (in the directory
content/) is used in two ways, for two purposes.
The first purpose is to keep the XML chunks of
a DocBook document, in order to keep the history
of modifications and in order to synchronize
the workspace and the public space. The
synchronization happens when the changes are
approved. For this purpose, a different subversion
repository is created for each book and for each
language, which keeps the chunks of a single
(exploded) docbook document. The directory that
keeps these repositories is 'content/books/svn/'.
Creating a separate repository for each document
is a design decision. If you think that it could
have been done better, we can disscuss the advantages
and dissadvantages of it at:
[EMAIL PROTECTED]
If you convince me that you are right, then I can
plan to change it in the future.
The second purpose is to keep the whole (imploded)
docbook documents. This purpose is totally unrelated
to the first one. The directory used for this
purpose is 'content/SVN/'. Have a look also at
'content/SVN/book_list.sh'. The aim of the SVN
directory (and the scripts in it) is to maintain
the whole (imploded) documents that we edit.
After all we are not interested in the chunks,
we are interested in the docbook documents; the
chunks are used just to make the editing easier
and more efficient. The repository that is used
for this purpose can be local (which is the
default case), or it can be remote. Why would
somebody need to keep the documents in a remote
repository? There can be some resons, e.g. the
editing can be done in one server and the public
display in another; or half of the documents can
be editied in one server and the rest in another,
and they can be synchronized with each other
easily.
Coming back to the problem that you describe here,
I think that you maybe forgot to do these things:
1 - After importing a new book you should also
add an entry for it in
'content/SVN/book_list.sh'
(maybe this should be done automatically by
the system, I am not sure about it)
2 - After making changes to the book, you should
approve and commit them. This would synchronize
the workspace and the public copy, and the
changes would appear in the imploded docs,
downloads etc. (because the public copy
is imploded by default).
So, after doing these, the 'straight' (normal) way
to make downloads would be like this:
bash$ make downloads
or
bash$ content/downloads/make-all-downloads.sh
and the new books and the new changes would appear
(assuming that everything else worked ok).
I hope that I have explained it well.
Regards,
Dashamir
--- Torsten Schlabach <[EMAIL PROTECTED]> wrote:
> Hi!
>
> I am still trying to fully understand the role of
> SVN (not for the code,
> for the books) in DocbookWiki.
>
> What I found out as a potential reason my creating
> the downloadables
> does not work for my own books: They don't seem to
> end up where they belong.
>
> Here is what I got when importing a book from the
> web frontend:
>
> Exploding 'ppguide'
> initial_xml/uploaded/deletemetoo.xml
> chmod: changing permissions of `explode/tmp/':
> Operation not permitted
> Creating svn repository books/svn/ppguide/en
> Importing into:
>
file:///var/www/virtual/docbook.rent-a-wiki.com/book-cvs-20060329/content/books/svn/ppguide/en/trunk
>
> Committed revision 2.
> Checking out to books/xml/ppguide/en/
> Checking out to workspace/xml/ppguide/en/
> Creating cache files in books/cache/ppguide/en/
> Creating cache files in workspace/cache/ppguide/en/
> Creating files state.txt in
> workspace/xml/ppguide/en/
> ----------
>
> Is it by purpose that a new SVN *repository* is
> created for my book?
>
> Taking a look at make-all-downloads.sh I get the
> impression that the
> plan was to keep all books in the same SVN
> repository? This would lead
> to checkout_xml_sources.sh copying *all* book into
> xml_sources thus
> make-downloads.sh finding my new book actually.
>
> I have edited my new book and tried to manually
> implode it to get a
> one-file docbook document that I would copy into
> xml_sources manually.
>
> But I don't know what implode.sh is picking up. It
> says:
>
> Imploding 'ppguide/en' to implode/tmp/ppguide.xml
>
> But the resulting file is the initial version, not
> the edited content.
>
> I need some hints here! Does it break all the way in
> the first place
> when the imported book does not end up where it
> should?
>
> Regards,
> Torsten
>
>
>
-------------------------------------------------------
> Using Tomcat but need to do more? Need to support
> web services, security?
> Get stuff done quickly with pre-integrated
> technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1
> based on Apache Geronimo
>
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Doc-book-users mailing list
> [email protected]
>
https://lists.sourceforge.net/lists/listinfo/doc-book-users
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Doc-book-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/doc-book-users
