Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33

To: tech-pkg%netbsd.org@localhost
Subject: Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
From: Joerg Sonnenberger <joerg%britannica.bec.de@localhost>
Date: Sun, 10 Nov 2013 21:00:24 +0100

On Sun, Nov 10, 2013 at 07:57:30PM +0000, David Holland wrote:
> However, this first really needs to be rolled into pkgsrc's own
> depends handling.

Python versions are handled correctly IFF both packages support the same
set.

Joerg

Follow-Ups:
- Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
  - From: David Holland

References:
- pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
  - From: Richard PALO
- Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
  - From: David Holland
- Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
  - From: Greg Troxel
- Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
  - From: David Holland

Prev by Date: Re: gimp upstream report?
Next by Date: Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
Previous by Thread: Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
Next by Thread: Re: pkg_chk (and consequently pkg_rolling_replace) confused with PYTHON_VERSION_DEFAULT=33
Indexes:

Home | Main Index | Thread Index | Old Index