Hi all,
I need to upgrade to 2.8.10. Mandriva repo contains 2.8.9 which
doesn't match with the demo I downloaded. Also the latest contains
more fixes (is that right?). So how to do that? Is there an rpm
somewhere? Some times ago I saw some work around for ubuntu/debian to
add latest wxPy to repo. Is there work around for mandriva?
IF it is not too much asking, why is there no rpm? Is it so hard to
generate? what takes to do it?
thanks
evstevemd a �crit :
Hi all,
I need to upgrade to 2.8.10. Mandriva repo contains 2.8.9 which
doesn't match with the demo I downloaded. Also the latest contains
more fixes (is that right?). So how to do that? Is there an rpm
somewhere? Some times ago I saw some work around for ubuntu/debian to
add latest wxPy to repo. Is there work around for mandriva?IF it is not too much asking, why is there no rpm? Is it so hard to
generate? what takes to do it?thanks
Hello,
The only way I know and tested is to compile from source.
I don't know how to do a rpm.
Cheers.
Hi all,
I need to upgrade to 2.8.10. Mandriva repo contains 2.8.9 which
doesn't match with the demo I downloaded. Also the latest contains
more fixes (is that right?). So how to do that? Is there an rpm
somewhere? Some times ago I saw some work around for ubuntu/debian to
add latest wxPy to repo. Is there work around for mandriva?
Either ask the package maintainer for Mandriva what their plans for it are, or build it yourself by taking the spec file from the current package and updating it for the new version.
IF it is not too much asking, why is there no rpm? Is it so hard to
generate? what takes to do it?
I stopped building binary RPMs for a couple reasons:
1. I no longer use an RPM-based distro myself.
2. Most of the major RPM-based distros are already providing wxPython RPMs in their repositories, or in some popular repository maintained by a 3rd party.
3. Each of them either made changes to the RPMs I produced, or completely reimplemented the spec file, because of various standards and policies that the packages for each distro is supposed to follow.
Either ask the package maintainer for Mandriva what their plans for it
That's pretty hard because I don't know how to
are, or build it yourself by taking the spec file from the current
package and updating it for the new version.
This is pretty comfortable than first on but how do I do it?
> IF it is not too much asking, why is there no rpm? Is it so hard to
> generate? what takes to do it?I stopped building binary RPMs for a couple reasons:
1. I no longer use an RPM-based distro myself.
2. Most of the major RPM-based distros are already providing wxPython
RPMs in their repositories, or in some popular repository maintained by
a 3rd party.3. Each of them either made changes to the RPMs I produced, or
completely reimplemented the spec file, because of various standards and
policies that the packages for each distro is supposed to follow.
would you provide simple tutorial on building RPM at wxPython site/
Wiki
--
Robin Dunn
Software Craftsmanhttp://wxPython.org
Great thanks Rob!
Either ask the package maintainer for Mandriva what their plans for it
That's pretty hard because I don't know how to
The package maintainer's email address is usually part of the metadata of the RPM.
are, or build it yourself by taking the spec file from the current
package and updating it for the new version.This is pretty comfortable than first on but how do I do it?
* Get the current source RPM from the whatever repository is making the binary RPMs available to you.
* Extract the .spec file from it. Update it to use the new version of the wxPython source code.
* You may need to read any packaging policy documentation that Mandriva provides to understand some of what is already in the spec file, and what you need to do to update for the new version. There are also some general docs about RPM out on the Net that will give you more info about the structure of the spec file and how to maintain it.
* Use the rpmbuild command to make binary RPMs from the new spec file and the new source tarball.
I failed miserably
How do I do that using only sources? No rpm thing
On Dec 31 2009, 11:57 pm, Robin Dunn <ro...@alldunn.com> wrote:
On 12/31/09 1:24 AM, evstevemd wrote:
>> Either ask the package maintainer for Mandriva what their plans for it
> That's pretty hard because I don't know how toThe package maintainer's email address is usually part of the metadata
of the RPM.>> are, or build it yourself by taking the spec file from the current
>> package and updating it for the new version.> This is pretty comfortable than first on but how do I do it?
* Get the current source RPM from the whatever repository is making the
binary RPMs available to you.* Extract the .spec file from it. Update it to use the new version of
the wxPython source code.* You may need to read any packaging policy documentation that Mandriva
provides to understand some of what is already in the spec file, and
what you need to do to update for the new version. There are also some
general docs about RPM out on the Net that will give you more info about
the structure of the spec file and how to maintain it.* Use the rpmbuild command to make binary RPMs from the new spec file
and the new source tarball.--
Robin Dunn
Software Craftsmanhttp://wxPython.org
I have tried instruction in thelink below but ./configure runs fine
while make fails
here is output
------------------------------------------------------------
[root@localhost wxPython-src-2.8.10.1]# make
make: *** No rule to make target `/home/stefa/Downloads/wxPython-
src-2.8.10.1/lib/wx/include/gtk2-ansi-release-2.8/wx/setup.h', needed
by `.pch/wxprec_basedll/wx/wxprec.h.gch'. Stop.
[root@localhost wxPython-src-2.8.10.1]#
----------------------------------------------------------------
Link I used (old): http://wiki.wxpython.org/How%20to%20install%20wxPython
On Jan 17, 4:02 pm, evstevemd <mwinjili...@gmail.com> wrote:
I failed miserably
How do I do that using only sources? No rpm thingOn Dec 31 2009, 11:57 pm, Robin Dunn <ro...@alldunn.com> wrote:
> On 12/31/09 1:24 AM, evstevemd wrote:
> >> Either ask the package maintainer for Mandriva what their plans for it
> > That's pretty hard because I don't know how to> The package maintainer's email address is usually part of the metadata
> of the RPM.> >> are, or build it yourself by taking the spec file from the current
> >> package and updating it for the new version.> > This is pretty comfortable than first on but how do I do it?
> * Get the current source RPM from the whatever repository is making the
> binary RPMs available to you.> * Extract the .spec file from it. Update it to use the new version of
> the wxPython source code.> * You may need to read any packaging policy documentation that Mandriva
> provides to understand some of what is already in the spec file, and
> what you need to do to update for the new version. There are also some
> general docs about RPM out on the Net that will give you more info about
> the structure of the spec file and how to maintain it.> * Use the rpmbuild command to make binary RPMs from the new spec file
> and the new source tarball.> --
> Robin Dunn
> Software Craftsmanhttp://wxPython.org
I have tried instruction in thelink below but ./configure runs fine
Did you just run a bare configure or did you use any command line options? If so which ones? See http://wxpython.org/builddoc.php
while make fails
here is output
------------------------------------------------------------
[root@localhost wxPython-src-2.8.10.1]# make
make: *** No rule to make target `/home/stefa/Downloads/wxPython-
src-2.8.10.1/lib/wx/include/gtk2-ansi-release-2.8/wx/setup.h', needed
by `.pch/wxprec_basedll/wx/wxprec.h.gch'. Stop.
[root@localhost wxPython-src-2.8.10.1]#
Try making an empty dir to do the build in, and then run configure from there.