Bug#463807: RFH: wxwidgets2.8 -- help for wxwidgets2.8 is appreciated

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#463807: RFH: wxwidgets2.8 -- help for wxwidgets2.8 is appreciated

Ryan Niebur
I will help with this, in hopes that a new version will be more stable
and fix the libwx-perl FTBFS bugs. Padre upstream strongly recommends
(by not allowing installation with older versions, unless we patch the
build system, which is what we did) the next version of wxwidgets
after what we have, because the version we have is "buggy".

Despite my only exposure to wxwidgets being through the Perl bindings,
and only using them since last week, I will be willing to work on this
package in the long term to keep it in shape for Padre.

I can probably help with RC bug fixing, upgrading to new upstream
versions, reviewing and applying patches, fixing trivial bugs,
forwarding/triaging bugs, and keeping the packaging in good shape, but
probably won't be very helpful for anything that requires a lot of
knowledge of wxwidgets, C++, or Python, since I don't know these.

Adeodato, may I start working and commit to the Git repository?

--
_________________________
Ryan Niebur
[hidden email]

signature.asc (204 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#463807: RFH: wxwidgets2.8 -- help for wxwidgets2.8 is appreciated

Ryan Niebur
On Tue, Jun 30, 2009 at 03:36:06PM -0700, Ryan Niebur wrote:

> I will help with this, in hopes that a new version will be more stable
> and fix the libwx-perl FTBFS bugs. Padre upstream strongly recommends
> (by not allowing installation with older versions, unless we patch the
> build system, which is what we did) the next version of wxwidgets
> after what we have, because the version we have is "buggy".
>
> Despite my only exposure to wxwidgets being through the Perl bindings,
> and only using them since last week, I will be willing to work on this
> package in the long term to keep it in shape for Padre.
>
> I can probably help with RC bug fixing, upgrading to new upstream
> versions, reviewing and applying patches, fixing trivial bugs,
> forwarding/triaging bugs, and keeping the packaging in good shape, but
> probably won't be very helpful for anything that requires a lot of
> knowledge of wxwidgets, C++, or Python, since I don't know these.
>
> Adeodato, may I start working and commit to the Git repository?
>
oops, I guess I should ask Ron instead since he's the admin for the
alioth project. Ron, can you add me to the project? (ryan52-guest in
alioth).

--
_________________________
Ryan Niebur
[hidden email]

signature.asc (204 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#463807: RFH: wxwidgets2.8 -- help for wxwidgets2.8 is appreciated

Adeodato Simó-4
In reply to this post by Ryan Niebur
+ Ryan Niebur (Tue, 30 Jun 2009 15:36:06 -0700):

> I will help with this, in hopes that a new version will be more stable
> and fix the libwx-perl FTBFS bugs. Padre upstream strongly recommends
> (by not allowing installation with older versions, unless we patch the
> build system, which is what we did) the next version of wxwidgets
> after what we have, because the version we have is "buggy".

> Despite my only exposure to wxwidgets being through the Perl bindings,
> and only using them since last week, I will be willing to work on this
> package in the long term to keep it in shape for Padre.

> I can probably help with RC bug fixing, upgrading to new upstream
> versions, reviewing and applying patches, fixing trivial bugs,
> forwarding/triaging bugs, and keeping the packaging in good shape, but
> probably won't be very helpful for anything that requires a lot of
> knowledge of wxwidgets, C++, or Python, since I don't know these.

> Adeodato, may I start working and commit to the Git repository?

Please go ahead, thank you!

Regarding 7eb273055220d815c39075c8655407514b1764c2, it seems I didn't
put a rationale in the commit message, but all I can say is that I think
I produced clean packages, so I'd venture the *.mo files get cleaned in
some other way, or they don't need cleaning.

Cheers,

--
- Are you sure we're good?
- Always.
        -- Rory and Lorelai




--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]