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

[Andre W. <wo...@us...>]

Hi,

On 08.05.04, Faheem Mitha wrote:
> > 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'm not aware of a support to build different kind of source packages
within Pythons distutils.

> 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.

I suggest to skip the pdfs in the source distribution. This seems to
be the only meaningful solution. We should prepare and distribute a
separate documentation file containing *only* the precompiled pdf
files.

> > > Also, there appears to be no way to generate examples/examples.pdf from
> > > source. Is that correct?
> 
> I think it would be useful to make it possible to build it. For
> example, the pdf could be built with different options...

Ok, I've modified MANIFEST.in accordingly.

> 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'll try this out tonight (I don't have my debian unstable box here)
and see, whether I'm able to reproduce/solve/whatever the problem.

BTW the whole discussion about latex2html is certainly interesting. On
the other hand we're not forcing latex2html ourselfs. Its just the way
the python documentation utilities currently work. It allows us to put
a html-version of the documentation online -- which is nice. For local
usage the pdf documents might be ok skipping the issue of latex2html
completely. As far as I am concerned its a minor point whether you are
able to provide a python-pyx-doc-html or not.


André

-- 
by  _ _      _    Dr. André Wobst
   / \ \    / )   wo...@us..., http://www.wobsta.de/
  / _ \ \/\/ /    PyX - High quality PostScript figures with Python & TeX
 (_/ \_)_/\_/           visit http://pyx.sourceforge.net/