On Wednesday 03 October 2012 16:14:51 Erik Hanson wrote:
> On Wed, 3 Oct 2012 14:59:16 -0500
> 
> Erik Hanson <e...@slackbuilds.org> wrote:
> > On Wed, 3 Oct 2012 15:42:00 -0400
> > 
> > B Watson <yalh...@gmail.com> wrote:
> > > On 10/3/12, Daniil Bratashov <dn2...@gmail.com> wrote:
> > > > It seems to me that MacMolPlt should be using wxGTK, not wxPython as
> > > > dependency. May be I don't understand something why it was replaced.
> > > 
> > > As I understand it, wxPython includes wxGTK. Anything that uses wxGTK
> > > can
> > > use either...
> > > 
> > > Maybe the two builds should be merged?
> > 
> > wxGTK was dropped for the above reason.
> 
> Sorry, I spoke too soon. We had a conversation about dropping wxGTK and
> wxX11, but it never happened. However, I think Matteo has a small fix for
> wxPython that should make it work with wxmacmolplt in place of wxGTK.

While I don't really mind if wxGTK and wxX11 get removed, there really is no 
necessity to do so IMHO. They are separate upstreams with separate release 
schedules (which came in handy already once in the past). If the maintainers 
still feel like maintaining them and want to provide users the option to pick, 
why not? For avoiding conflicts in dependency management? On slackware?

Grs,
Heinz

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - http://slackbuilds.org/faq/

Reply via email to