[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
python packages with included eggs
py-zfec's distfile has an included egg for "darcsver", used to find
version number from a darcs repository. It's easy enough to package,
but I haven't added py-darcsver yet. Instead, py-zfec's build uses the
Obviously it's uncool for a build to download things, and python
setuptools will do that for unsatisfied dependencies. But using an
included egg seems more like having ocnfigure already generated from
Should we adopt a "use of included eggs bad, package them and depend
on them good" notion?
If not, should I add py-darcsver anyway, on the theory that having a
separate package is nicer.
--- Begin Message ---
Module Name: pkgsrc
Committed By: gdt
Date: Sat Jul 24 13:24:15 UTC 2010
Update of /cvsroot/pkgsrc/converters/py-zfec
In directory ivanova.netbsd.org:/tmp/cvs-serv29605
Import py26-zfec-1.4.7 as converters/py-zfec.
A fast erasure codec which can be used with the command-line, C,
Python, or Haskell.
Fast, portable, programmable erasure coding a.k.a. "forward error
correction": the generation of redundant blocks of information such
that if some blocks are lost then the original data can be recovered
from the remaining blocks. The zfec package includes command-line
tools, C API, Python API, and Haskell API.
Vendor Tag: TNF
Release Tags: pkgsrc-base
No conflicts created by this import
--- End Message ---
Main Index |
Thread Index |