Re: [PyX-devel] minor comments about 0.6.3 tarball, Debian package for PyX 0.6.3

[Faheem M. <fa...@em...>]

On Mon, 3 May 2004, Andre Wobst wrote:

> Hi,
>
> On 01.05.04, Faheem Mitha wrote:
> > svn-buildpackage got upset becasuse the upstream tarball contains
> > manual/manual.pdf, but this gets cleaned by `make clean' and gets built=
 by
> > make, so it looks like it should not be there in the upstream tarball. =
The
> > same comments apply to faq/pyfaq.pdf.
>
> I think there is difference between creating a source package (for
> debian or similar) and our distribution of PyX. We include a
> precompiled version of the manual and faq to make it easier for the
> user to become familiar with PyX. You are right, you can create both
> documents from the source, which is also included in the distribution.
> But in order to build the pdf files you already have to setup your
> environment properly (Python, TeX, etc.). However, when building a
> source package for a distribution, those pdf files are not *source*
> files and should not be part of a source package.

Yes, I see. It would optimal if you could ship a separate source-only
tar.gz not containing any pdfs. This would save on space on mirrors
and could be used by people who only want the source. Currently around
half the source by size consists of the pdfs.

> > I've considering removing these from the upstream tarball and rebuildin=
g
> > it, but I thought I would ask here first, since the tarball is supposed=
 to
> > correspond to pristine sources. Perhaps the *.pdf files were provided f=
or
> > people who don't want to build their own docs? It was not there in the
> > 0.4.1 version in the official Debian package (I have not checked the
> > others). It does make the tarball rather big.
>
> Feel free do create the package the way it suits best to the policy of
> the distribution. Nothing else matters as far as I am concerned.

Debian's policy is to ship a copy of the pristine upstream sources (as
*.orig.tar.gz) along with a diff. Pristine in the sense that the
md5sums of the source shipped should match that of the source from
upstream. So the above is not an option.

> > Also, there appears to be no way to generate examples/examples.pdf from
> > source. Is that correct?
>
> Yes. I consider example.pdf to be not at all usefull, once you can run
> the examples yourself. We've build and included the pdf for promotion
> only. I would suggest to take the source of the examples as parts of
> the documentation without taking care of the examples.pdf. However we
> may provide the build script in future as well (its available via CVS
> already, of course) if there are strong demands for that ...

I think it would be useful to make it possible to build it. For
example, the pdf could be built with different options...

> > Also, I ran into errors when trying to build manual.html. I'd appreciat=
e
> > assistance on this, though the error messages were not very useful, so =
I
> > am not sure how much information I can provide.
>
> You need to create a symbolic link of mkhowto from the python
> documentation tools (Do not just copy the file, since it uses the
> symlink to find further files it requires). In case this doesn't
> already solve your problem, feel free to post a little more
> information about your problem. But I'm not an expert in pythons
> documentation tools ... I just worked it out how to get it running
> myself (on fink, J=F6rg now uses it on debian as well). May be there
> somebody on this list, who has a better knowlegde of pythons
> documentation utils once we know a little more about your problem.

I put the PyX packages I produced online. They are the latest version:
0.6.3. Add the following to your sources.list, and you can get them.
 You can also get the sources by using deb-src.

deb http://www.stat.unc.edu/students/faheem/debian/ ./
deb-src http://www.stat.unc.edu/students/faheem/debian/ ./

If you download the sources and rename debian/rules.broken to
debian/rules, and then try to rebuild the debs on a Debian
testing/unstable machine, you should be able to reproduce the problem I
was seeing.

I can send you the error log, but it is not very informative.

1) as root do

apt-get build-dep python2.3-pyx
apt-get install devscripts latex2html

2) Do

apt-get source python2.3-pyx

as user in some scratch directory

3) Type

debuild binary

in the subdirectory pyx-0.6.3 produced.

The official Debian maintainer of PyX just uploaded packages, but he
doesn't build html files either.

Please CC me. I'm not subscribed. Thanks.
                                                          Faheem.