I’ve email previously on this, but the eclasses have been through a bit
of a change since then.
postgres.eclass has some common functions and initializes some variables
that are used in many of the PostgreSQL-related packages.
postgres-multi.eclass makes it possible to install one package (e.g.,
2017-04-21 18:21 GMT+02:00 Jörg Schaible :
> Walter Dnes wrote:
>
> > On Thu, Apr 20, 2017 at 05:52:20PM -0500, Matthias Maier wrote
> >
> >> (A-C) gcc-5.4.0 and gcc-4.9.4 are slotted separately. What is going to
> >> be the default is entirely up to you.
> >
> > Good to hear. Like I said, on a
Walter Dnes wrote:
> On Thu, Apr 20, 2017 at 05:52:20PM -0500, Matthias Maier wrote
>
>> (A-C) gcc-5.4.0 and gcc-4.9.4 are slotted separately. What is going to
>> be the default is entirely up to you.
>
> Good to hear. Like I said, on a fresh install I'd go with the current
> version (5.4).
Use plain 'pythonX.Y-config' executable name in the python-config
wrapper instead of querying the complete PYTHON_CONFIG path from
python_export.
Constructing full PYTHON_CONFIG path requires querying ABIFLAGS which
requires the Python interpreter to be installed, which in turn
unnecessarily force
On Thu, 20 Apr 2017 10:49:04 -0700
Christopher Head wrote:
> >Usually when writing new code, you use the latest version of stuff. Not
> >always but usually best. If anything make code support older while
> >targeting newer.
>
> No, not how I develop. I always start by determining my target aud
