Re: [ jEdit-devel ] Line numbers in the gutter

[Kazutoshi S. <k_s...@f2...>]

Kevin Hunter wrote:
> Do we need a checklist?

I want it, especially if people will check it.

It will be:
  - ensure it builds.
  - exclude unnecessary or irrelevant changes.
  - don't mix multiple changes.
  - ensure that a summary and the reason (justification) of change
    can be read from the log message.
  - put related links to bug, feature request, patch, or mailing list
    discussion in the log message, if any.
  - for user visible change, add a note in CHANGES.txt, and consider
    updating the corresponding user-doc by the way.
... and so on.

>> One thing no less important than this, is the update of the user docs
>> of jEdit. I don't do that both because I forget, and because I don't
>> have the infrastructure for building the jEdit docs. If this could
>> somehow be simplified, it would be great help. In this specific case,
>> I think the addition of a GUI option should be added to the user docs.
> 
> I'm curious about the infrastructure bit.  I know that for Debian based
> distribution, it's a matter of 'apt-get' plus a few packages.  Would
> enumerating those packages for different distros be of help or use to
> anyone?

I, as a Windows user, also had tried several times to setup a full
environment to build the docs, and dist package. Fortunately I could
make it working with the followings in build.properties.

### The name of the Inno Setup compiler executable
### for building of the Windows installer
innosetup.compiler.executable=C:\\Program Files\\Inno Setup 5\\Compil32.exe

### For generating the docs adjust the following to your local paths
### For xsltproc to work, the path to the DocBook stuff MUST NOT contain spaces!
xsltproc.executable=C:\\cygwin\\bin\\xsltproc
docbook.xsl=C:\\cygwin\\usr\\share\\docbook-xsl
docbook.catalog=C:\\cygwin\\usr\\share\\xml\\docbook\\4.4\\docbook.cat

I hope this can help others.
-- 
k_satoda