On Tue, Oct 19, 2010 at 01:28:26PM +1100, Ben Finney wrote:
> Chris Ball <[email protected]> writes:
> 
> >    > That is, have the release tarball exclude the ‘.git/’ directory
> >    > and include the ‘libbe/_version.py’ auto-generated file.
> >
> > I think the "python setup.py build/install" path will end up calling
> > make, which will end up calling git, which will fail.
> 
> To make that work, the Makefile rules should be such that when the
> ‘libbe/_version.py’ file is already up to date, then no ‘git’ command is
> necessary.

Except libbe/_version.py is marked .PHONY in the Makefile, since the
Makefile can't tell if it's up to date unless it knows Git.  The solution
is

  1) Generate libbe._version while you're still in Git.
  2) In the Makefile, change  'build: libbe/_version.py'  ->  'build:'
  3) Set libbe.version._VERSION

I've altered release.py in my branch to also do (2) (+ some bzr->git
migrations).  It already did (1) and (3).

On Tue, Oct 19, 2010 at 12:54:04PM +0200, Elena ``of Valhalla'' wrote:
> Generating the documentation under e.g. Arch Linux is problematic
> because of issues with the sphinx version and the lack of
> legacy prerequisites for docbook-to-man

My commit:

  commit 8c9f876ae69f7bf92686edea320931d875b5c681
  Author: W. Trevor King <[email protected]>
  Date:   Tue Sep 28 21:25:43 2010 -0400

  Converted man page source to DocBook V5.0.

Does not seem to have been merged into the trunk yet, but it replaces
the docbook-to-man dependency with xsltproc and the NS-enabled DocBook
stylesheets.  See
  http://www.physics.drexel.edu/~wking/code/be/doc/install.html
  http://www.physics.drexel.edu/~wking/code/be/doc/doc.html#man-page
  
I'm not sure if I posted anything about that to the list or not
though, sorry ;).

On Tue, Oct 19, 2010 at 07:45:37PM +0200, Gianluca Montecchi wrote:
> python setup.py install
>
> does not install the manpages, since they are not builded

You should install it with `make install` which generates the manpages
if they are missing.

-- 
This email may be signed or encrypted with GPG (http://www.gnupg.org).
The GPG signature (if present) will be attached as 'signature.asc'.
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt

Attachment: pgp4LNNIsvnmi.pgp
Description: PGP signature

_______________________________________________
Be-devel mailing list
[email protected]
http://void.printf.net/cgi-bin/mailman/listinfo/be-devel

Reply via email to