[MacPorts] #26387: xorg-xcb-proto/python dependency loop via tk/libX11
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch | Port: xorg-xcb-proto -------------------------------+-------------------------------------------- This ticket is a followup to Ticket #26381 While that ticket is now fixed, a dependency loop still remains between python and xorg-xcb-proto. The attached patch resolves this issue. -- Ticket URL: <http://trac.macports.org/ticket/26387> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: blb@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Changes (by jeremyhu@…): * keywords: haspatch => * owner: macports-tickets@… => blb@… * port: xorg-xcb-proto => python * cc: mcalhoun@… (added) Comment: We can't really do that because xorg-xcb-proto builds python modules. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: blb@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Comment(by jeremyhu@…): Why does python need tk? -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: blb@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Comment(by spyro@…): Unfortunately, tk is one of the core parts of python: http://docs.python.org/library/tk.html It is python's included gui framework. I suppose one could just use `port install python26 +no_tkinter`, but this would not really be a full python installation (it breaks IDLE, the dev environment included with python). Couldn't xorg-xcb-proto use the system python like xorg-libxcb did? -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: blb@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Comment(by jeremyhu@…): No. It's not just used to build. xorg-xcb-proto installs python modules. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: blb@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Comment(by spyro@…): So in that case, the patch that I created probably messed up my xorg-xcb- proto install? I suppose that the best thing to do would be: 1. To use `port install python26 +no_tkinter`[[BR]] 2. Then install xorg-xcb-proto normally[[BR]] 3. Then reinstall python without +no_tkinter I wonder if there is any way to streamline this process or atleast to make it more obvious? Thank you for your help! -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Changes (by blb@…): * cc: mcalhoun@… (removed) * owner: blb@… => mcalhoun@… -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:6> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: python -------------------------------+-------------------------------------------- Comment(by jmr@…): Dodgy workaround applied in r71286, since this is an "everything is broken!" situation from a new user's perpective. So, taking into account that tkinter is considered a core python module, and our tk port must depend on X11 on 64-bit platforms because the aqua variant uses Carbon, what are we going to do about this? -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:8> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Changes (by jmr@…): * port: python => xorg-xcb-proto python26 -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:9> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by jzwolak@…): Replying to [comment:5 spyro@…]:
So in that case, the patch that I created probably messed up my xorg- xcb-proto install?
I suppose that the best thing to do would be:
1. To use `port install python26 +no_tkinter`[[BR]] 2. Then install xorg-xcb-proto normally[[BR]] 3. Then reinstall python without +no_tkinter
I wonder if there is any way to streamline this process or atleast to make it more obvious?
Thank you for your help!
Here are the exact commands that worked for me: sudo port install python26 +no_tkinter sudo port -f activate python26 sudo port install xorg-xcb-proto sudo port clean python26 sudo port install python26 And then I can install ImageMagick, xorg, or whatever. Note that the second command may not be necessary on your system, it was necessary on mine because I had some files lying around from a previous Python installation attempt. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:10> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by jzwolak@…): Here's my previous post formated correctly:[[BR]] [[BR]] Here are the exact commands that worked for me:[[BR]] [[BR]] sudo port install python26 +no_tkinter[[BR]] sudo port -f activate python26[[BR]] sudo port install xorg-xcb-proto[[BR]] sudo port clean python26[[BR]] sudo port install python26[[BR]] [[BR]] And then I can install ImageMagick, xorg, or whatever. Note that the second command may not be necessary on your system, it was necessary on mine because I had some files lying around from a previous Python installation attempt. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:11> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by dluke@…): IIRC the python sub-ports were pulled back into the python main port because python -S won't load modules. Is tkinter something that needs to be run in that situation? My initial thought would be to just pull tkinter out into its own port (like we used to do with all of the python modules). If having it installed as a module doesn't brake IDLE, it might be the best (bad) fix. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:12> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Changes (by raimue@…): * cc: raimue@… (added) Comment: Replying to [comment:12 dluke@…]: Actually that would be what I suggested in [http://lists.macosforge.org/pipermail/macports-dev/2009-April/008236.html April 2009] already ;-) Another solution would be to move the python module xcbgen to its own port? -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:13> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by jeremyhu@…): Moving xcbgen to its own port won't help because we'll still need to depend on it in xorg-libxcb -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:14> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by dluke@…): Replying to [comment:13 raimue@…]:
Replying to [comment:12 dluke@…]: Actually that would be what I suggested in [http://lists.macosforge.org/pipermail/macports-dev/2009-April/008236.html April 2009] already ;-)
Yep :) Unless someone else comes up with an alternate solution, I think we need to go this route. -- Ticket URL: <http://trac.macports.org/ticket/26387#comment:15> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by dluke@…): ... any reason not to create py26-tkinter (based off of py24-tkinter) and move the +no_tkinter stuff into the main python26 port? (this has been broken for a while now). -- Ticket URL: <https://trac.macports.org/ticket/26387#comment:17> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by jmr@…): Nope. Please do. -- Ticket URL: <https://trac.macports.org/ticket/26387#comment:18> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 -------------------------------+-------------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: xorg-xcb-proto python26 -------------------------------+-------------------------------------------- Comment(by dluke@…): py26-tkinter added in r74547 -- Ticket URL: <https://trac.macports.org/ticket/26387#comment:19> MacPorts <http://www.macports.org/> Ports system for Mac OS
#26387: xorg-xcb-proto/python dependency loop via tk/libX11 --------------------------------------+------------------------------------- Reporter: spyro@… | Owner: mcalhoun@… Type: defect | Status: closed Priority: High | Milestone: Component: ports | Version: 1.9.1 Resolution: fixed | Keywords: Port: xorg-xcb-proto python26 | --------------------------------------+------------------------------------- Changes (by dluke@…): * status: new => closed * resolution: => fixed Comment: +no_tkinter incorporated into the main python26 port in r74548 (without a revbump) -- Ticket URL: <https://trac.macports.org/ticket/26387#comment:20> MacPorts <http://www.macports.org/> Ports system for Mac OS
participants (1)
-
MacPorts