On Sat, Mar 3, 2012 at 1:36 AM, gihan karunarathne <[email protected] > wrote:
> Hi, > > I followed the steps which are provided by you. Add path to the > DOCBOOK_SVN (used:https://help.ubuntu.com/community/EnvironmentVariables). > And checked using "echo" command. > > Open using "gedit ~/.bashrc" and add ". /home/gihan/docbk.sh" into the > bashrc file and saved it. > > Then follow the steps in README.BUILD > *-----------------------------------------------------------------* > *Part 1: Build and test the stylesheets* > *-----------------------------------------------------------------* > * 1.makeall* > > I got same error msg again as below; > > gihan@gihan-HP-Pavilion-dv6-Notebook-PC:~$ rm -f DOCBOOK-BUILD.LOG > gihan@gihan-HP-Pavilion-dv6-Notebook-PC:~$ . ~/docbk.sh > gihan@gihan-HP-Pavilion-dv6-Notebook-PC:~$ > $DOCBOOK_SVN/buildtools/build-clean > svn: warning: '.' is not a working copy > svn: warning: '.' is not a working copy > gihan@gihan-HP-Pavilion-dv6-Notebook-PC:~$ echo $DOCBOOK_SVN > /home/gihan/subversion/docbook/trunk > > build-clean file already exist in current location. But what is it mean by '.' > is not a working copy > Hi, I had look at the build-clean script to understand what caused this issue. Apparently, you should be inside your $DOCBOOK_SVN directory to perform this task. Since it runs the command `svn status` in the current folder (which is specified by a dot .), if you ran it from your home directory it won't work. '.' is not a working copy means that your current directory is not under svn version control. So, `cd $DOCBOOK_SVN` before invoking your command chain. Regards, --Kasun > Thank you in Advance ! > > Regards, > --Gihan > > On Fri, Mar 2, 2012 at 9:08 AM, Kasun Gajasinghe <[email protected]>wrote: >> >> >> Hi, >> I'd say, just create a file named docbk.sh at any location you want but >> remember the full path to it. The content for this are given in step 3 of >> README.BUILD. There, you need to make sure the 'export' paths are correct. >> For example, DOCBOOK_SVN should point to your DocBook svn checkout >> directory. >> >> After that, open up ~/.bashrc (by command gedit ~/.bashrc). This file is >> located at /home/your-account-name/.bashrc. "~/" is an alias. Now, instead >> of adding ". ~/docbk.sh" to that file as said in the README.BUILD, add the >> following. >> . /add/full/path/to/docbk.sh >> >> Don't worry about this much. It's a simple procedure. I suspect that the >> error you are getting "*svn: warning: '.' is not a working copy*" is >> because DOCBOOK_SVN is not set correctly. Can you run the command `echo >> $DOCBOOK_SVN` and see whether it outputs the correct directory? >> >> Regards, >> --Kasun >> >> >>> >>> Thank You in Advance !. >>> >>> regards, >>> Gihan Chanuka >>> >>> On Thu, Mar 1, 2012 at 10:44 PM, <[email protected]> wrote: >>> >>>> ** >>>> Gihan, >>>> >>>> You are referring to the instructions in the source tree that enumerate >>>> the steps required for building a "release" package. This is for the >>>> developers who preprocess/build each release that shows up on SourceForge. >>>> This is not a normal process for users of DocBook. >>>> >>>> The normal usage for user would be to download the ZIP file of the >>>> release and set up your XSLTPROC (or other tools) to run against that >>>> release. >>>> http://sourceforge.net/projects/docbook/files/docbook-xsl/ >>>> >>>> >>>> The XSLT processors transform the DocBook XML into HTML, PDF, EPUB, >>>> etc, via the XSL stylesheets in the release package. >>>> >>>> I would also suggest that you read the Bob Stayton's book on DocBook >>>> http://www.sagehill.net/docbookxsl/index.html also available in paper >>>> copy. >>>> >>>> Regards, >>>> Dean Nelson >>>> >>> > -- ~~~*******'''''''''''''*******~~~ *Kasun Gajasinghe* Software Engineer; WSO2 Inc.; http://wso2.com, *linked-in: *http://lk.linkedin.com/in/gajasinghe* * *blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org/> * twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
