On Wed, 23 Nov 2005, "Martin v. Löwis" wrote:
[...]
> I don't see how the maintainer could use the dependency information
> in the egg files.
The maintainers could use the dependency information in the egg files by
writing a tool to automatically map from the egg dep info to whatever
format their
On Tue, 22 Nov 2005, John J Lee wrote:
[...]
> Actually, I believe this is the eventual primary intended mode of
> operation of eggs. In that case, the necessary sys.path manipulation is
> handled either by setuptools' wrapper scripts / wrapper .exe files calling
> require(versio
On Tue, 22 Nov 2005, Phillip J. Eby wrote:
> At 11:56 PM 11/22/2005 +0100, Martin v. Löwis wrote:
> >Phillip J. Eby wrote:
> >>>Debian should provide the packages, but not as eggs.
> >>
> >>For packages that only operate as eggs, and/or require their dependencies
> >>as eggs, you are stating a co
On Tue, 22 Nov 2005, "Martin v. Löwis" wrote:
> > As
> > I've already stated, applying this same policy to Java libraries would
> > be to demanding that all the .class files be extracted to the filesystem
> > and any manifest files be deleted, before Debian would consent to
> > package them. I
4 matches
Mail list logo
