...at the same time.
Let's see, what we can do now (based on the ports, ignoring pkg here for
now):
- switch the default python version (for all ports) or the python
version for a single port
- properly install and deinstall all ports for python 2.x
- properly install and deinstall ports for py
On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote:
> ...at the same time.
>
> Use PKGNAMEPREFIX/SUFFIX for python ports
>
> - this is a clean up task (which should be done regardless of everything
> else). Some python modules miss the prefix, making it impossible to
> install them fo
On, Sat Aug 03, 2013, David Naylor wrote:
> On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote:
> > ...at the same time.
> >
> > Use PKGNAMEPREFIX/SUFFIX for python ports
> >
> > - this is a clean up task (which should be done regardless of everything
> > else). Some python modules miss
On Saturday, 3 August 2013 14:58:04 Marcus von Appen wrote:
> On, Sat Aug 03, 2013, David Naylor wrote:
> > On Saturday, 3 August 2013 12:32:45 Marcus von Appen wrote:
> > > Support for non-CPython implementations:
> > >
> > > - A mid-term goal should be to offer support PyPy in USE_PYTHON, etc.
>
03.08.2013 15:29, David Naylor пишет:
> I think not all python based ports should use PKGNAMEPREFIX/SUFFIX. Those
> are
> ports who's main contribution is a bin/ and not libraries. In these cases
> the
> use of python is largely incidental. Two example are devel/eric4
The port itself does
