On 01/09/2015 02:39 PM, Rich Shepard wrote:
On Fri, 9 Jan 2015, Mario Preksavec wrote:
You are very welcome, although it would probably make more sense to
clean
up paths in configuration files and avoid post-install file
hackery... :-)
Mario,
That does make sense, but there were no path c
On Mon, 12 Jan 2015, Heinz Wiesinger wrote:
Now one year has passed since wxPython 3.0 and nothing really changed. As
far as I'm concerned, I don't mind waiting a while longer.
FWIW, I've used wxPython-3.0.1.1 with Python-2.7.5 just fine. I expect
that wxPython-3.0.2.0 will continue working
On Mon, 12 Jan 2015, Matteo Bernardini wrote:
sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on
Heinz toes) switching to wxPython-3.x for all the stuff we have in out
repository isn't gonna be that easy. ATM, wxPython is needed by this stuff
on our repository
Matteo,
Th
On Monday 12 January 2015 11:02:54 Ryan P.C. McQuen wrote:
> On Jan 12, 2015 10:58 AM, "Matteo Bernardini"
> > sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on
> > Heinz toes) switching to wxPython-3.x for all the stuff we have in out
> > repository isn't gonna be that easy.
maybe the packages should be separated?
On Jan 12, 2015 10:58 AM, "Matteo Bernardini"
wrote:
> 2015-01-12 19:28 GMT+01:00 Rich Shepard :
> > On Mon, 12 Jan 2015, Matteo Bernardini wrote:
> >
> >> is it compatible with all the stuff on SBo that needs wxPython?
> >
> >
> > Matteo,
> >
> > I don't
2015-01-12 19:28 GMT+01:00 Rich Shepard :
> On Mon, 12 Jan 2015, Matteo Bernardini wrote:
>
>> is it compatible with all the stuff on SBo that needs wxPython?
>
>
> Matteo,
>
> I don't know. I upgrade to the latest wxPython when I start a new project
> and it works for the applications I write. H
On Mon, 12 Jan 2015, Matteo Bernardini wrote:
is it compatible with all the stuff on SBo that needs wxPython?
Matteo,
I don't know. I upgrade to the latest wxPython when I start a new project
and it works for the applications I write. Heinz is the SBo package
maintainer, and I let him know
is it compatible with all the stuff on SBo that needs wxPython?
Matteo
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/
wxPython-3.0.2.0 (classic) was released at the end of last November. It
builds here with a version change from the script I used to build -3.0.1.1.
The version on SBo is in the 2.8.x.x series.
Rich
___
SlackBuilds-users mailing list
SlackBuilds-users@
Ciao,
the web page[1] of the package "q4wine" references an upstream home
page[2] that is down for serious troubles. Is it the case to change it
to the source code distribution page[3]?
TIA
P.S. I do not know what is other people's experience, but these days I
cannot do a thing with So
Ciao,
the page of the "icoutils" package still references release 0.26.0;
the latest release[2] is 0.31.0 available since May 2013. I was able to
build the latest revision on my Slackware 14.1 64-bit with the following
changes to the build script:
28c28
< VERSION=0.26.0
---
> VERSION=${VERS
11 matches
Mail list logo
