On Mon, Oct 08, 2001 at 12:09:59PM +0200, Bastian Kleineidam wrote:
> Anthony Roach wrote:
> Exactly. With Python 2.1 you will have to make a 2.1 compatible .deb
> package.
OK.
> Make a suggestion, a recommendation is too hard as some users might want to
> stick
>
&g
tall both, so the user
can use scons with either python. Perhaps I should put this in my control file
for scons:
Depends: python-scons|python2-scons
Recommended: python-scons, python2-scons
Or maybe Suggests? I'm not sure either of these will really do what I want.
--
Homepage: http://
On Thu, Oct 04, 2001 at 09:05:07PM -0500, Anthony Roach wrote:
> 4) libSCons (why put the -python on? There isn't ever going to be a non-python
>version if libSCons).
Well, after some trial and error, I realized I can't name a binary package
libSCons, because the name has to b
sion of python on
the system)
4) libSCons (why put the -python on? There isn't ever going to be a non-python
version if libSCons).
Any feedback is greatly appreciated.
--
Homepage: http://www.electriceyeball.com
Email: Anthony Roach <[EMAIL PROTECTED]>
PGP Key: http:
4 matches
Mail list logo