blob: 7ffe231b688c672cdc0258b4f65c513aeda21ac7 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
|
[This time to the list]
* W. Trevor King (wking@drexel.edu) wrote:
> On Tue, Jul 14, 2009 at 03:29:42PM +0100, James Rowe wrote:
> > Isn't there a bzr web interface that at least supports creating
> > tarballs/zips? It is pretty standard functionality for most other VCS'
> > web interfaces so I'm guessing there must be, but loggerhead seems not
> > to support it.
>
> Unfortunately, people would still need bzr to install the versioned source:
>
> libbe/_version.py:
> bzr version-info --format python > $@
I hadn't even seen that change go in. The last upstream change in the
version I have installed locally was by you on 2008-11-24.
> So you'll need a "release" target in the makefile to build a bzr-less
> install. While you're at it, you should probably compile the manpage
> too to remove the docbook-to-man dependency.
Maybe for others. Our packages just don't have the manpage as it is only
the "be help" text reformatted, the easy option is sometimes the right
one :) Also, I've just noticed that it has even less documentation in
the bzr tree[1] making its installation much less compelling unless your
packaging rules require a man page like Debians.
Out of curiosity why is the Makefile being used for this stuff anyway?
It is going to make it difficult to build locally when we finally get
around to merging. Examples: If distutils was being used exclusively it
would fix the #! lines in xml/*. We'd be able to point Python
$version_of_the_day at setup.py instead of having to sed the Makefile or
run setup and manually install other files.
Thanks,
James
1. http://pullcord.laptop.org:4000/revision/314.1.15/doc/be.1.sgml
|
