On 10/31/18, Tim Dickson via SlackBuilds-users
wrote:
> documentation, but if you use two build scripts, the documentation would
> need to be in different places to avoid loosing it if you had both
> installed, and just removepkg one of them.
That wouldn't happen. removepkg would notice the
On 31/10/2018 10:01, David Woodfall wrote:
On Wednesday 31 October 2018 09:54,
Slackbuilds Users put forth the proposition:
On 30/10/2018 17:59, Benjamin Trigona-Harany wrote:
On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
We have both python2 and python3 versions of six in a single
On Wednesday 31 October 2018 09:54,
Slackbuilds Users put forth the proposition:
> On 30/10/2018 17:59, Benjamin Trigona-Harany wrote:
> > On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
> > >
> > > We have both python2 and python3 versions of six in a single package in -
> > > current and it
On 30/10/2018 17:59, Benjamin Trigona-Harany wrote:
On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
We have both python2 and python3 versions of six in a single package
in -
current and it works just fine. I don't see why the package would
need to be
treated differently from other python
oups, sorry, thanks Matteo and Ben
On Tue, 30 Oct 2018 10:59:44 -0700
Benjamin Trigona-Harany wrote:
> On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
> >
> > We have both python2 and python3 versions of six in a single package in -
> > current and it works just fine. I don't see why the
On 2018-10-30 10:57 a.m., Heinz Wiesinger wrote:
We have both python2 and python3 versions of six in a single package in -
current and it works just fine. I don't see why the package would need to be
treated differently from other python libs. What am I missing here?
Grs,
Heinz
I don't think
On Tuesday, 30 October 2018 17:55:59 CET Tim Dickson via SlackBuilds-users
wrote:
> On 29/10/2018 12:44, Rich Shepard wrote:
> > On Mon, 29 Oct 2018, B Watson wrote:
> >> Do we need separate six and python3-six builds?
> >>
> >> Right now, six will build & install python3 support if python3 is
>
On Tue, 30 Oct 2018, Tim Dickson via SlackBuilds-users wrote:
six is a special case, as it is provides compatibility for scripts running
different versions of python. It is useful to be able to create 2 separate
packages though, a python2 version, and a python3 version (with different
package
On 29/10/2018 12:44, Rich Shepard wrote:
On Mon, 29 Oct 2018, B Watson wrote:
Do we need separate six and python3-six builds?
Right now, six will build & install python3 support if python3 is
installed on the build box. python3-six is identical, except (a) it
requires python3 in the .info
On 2018-10-29 5:44 a.m., Rich Shepard wrote:
On Mon, 29 Oct 2018, B Watson wrote:
Do we need separate six and python3-six builds?
Right now, six will build & install python3 support if python3 is
installed on the build box. python3-six is identical, except (a) it
requires python3 in the
On Mon, 29 Oct 2018, B Watson wrote:
Do we need separate six and python3-six builds?
Right now, six will build & install python3 support if python3 is
installed on the build box. python3-six is identical, except (a) it
requires python3 in the .info file and (b) it builds only the python3
On 10/29/18, B Watson wrote:
> Do we need separate six and python3-six builds?
Disregard previous email on this subject, I see that six has been updated
to only install python2 modules. I was looking at the slackonly binary
packages, not the latest SBo.
Apologies if I raised anyone's blood
12 matches
Mail list logo
