Shoebot
I note on https://github.com/shoebot/shoebot that installation instructions for OSX are out of date, but there is a suggestion for using macports with Python 2.5 and a comment about missing dependencies on MacPorts. However, when I do a port search for shoebot it returned 'no match for shoebot found'. Any suggestions, please? Thanks in anticipation. -u ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: help! - Python, Tkinter and IDLE
Apology accepted. Yes, I still have to decide which way to go. I was happy enough to revert back to Python 2.6.2 on OSX as it seemed the simpler solution. The problem that I also encountered at this time if interesting, is an unrelated Python issue. On reflection, I have decided that to port install py27-tkinter is a good way forward, as I would like also to install the PIL library, and I see I can port py27-pil, too. But, I have yet to implement the decision :) Thanks for your help. -A -Original Message- From: Ryan Schmidt To: uga...@talktalk.net CC: MacPorts Users Sent: Sat, 5 Apr 2014 0:46 Subject: Re: help! - Python, Tkinter and IDLE On Apr 4, 2014, at 06:54, uga...@talktalk.net wrote: > I do not believe I told you as you claim, 'And you told us you installed Tcl and Tk in /Library/Frameworks. So that could be a problem.' Sorry, I misremembered your original message, in which you said you had downloaded an installer that would install Tcl and Tk there, but that you had not run it yet. > As I have not ported Tcl/Tk, that cannot be the problem. > AFAIK to run IDLE Python requires Tcl/tk. Indeed, IDLE requires Tcl and tk. And installing the py27-tkinter port would install MacPorts Tcl and tk. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: help! - Python, Tkinter and IDLE
Yes I may try this, as I have resolved the problem. YEAY! Thanks, all. -A -Original Message- From: Lenore Horner To: MacPorts Users Sent: Fri, 4 Apr 2014 11:52 Subject: Re: help! - Python, Tkinter and IDLE I have attached a screen grab of the alert message which now appears when I try to run IDLE from OSX Python. The message box is itself frozen, and the OK button unresponsive. Eventually a shape the size of the IDLE window appears on screen as a blank white square, and I have to force quit, to quit the python launcher. In addition, this is the console message that appears in Terminal: Apples-iMac-4:scripts apple$ IDLE 11:20:00 Traceback (most recent call last): File "", line 1, in File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/idlelib/run.py", line 7, in import threading File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", line 14, in from time import time as _time, sleep as _sleep ImportError: cannot import name sleep The console message has identical content to a message that I am also currently investigating, and which had caused me to try to launch IDLE at this time. This problem relates to running Python scripts that have import commands to a particular 3rd party library, which were working, but now no longer work without generating the same console message. Other scripts seem to run OK on both OSX Python and the macported Python. I would say the problem is with the 3rd party library save that IDLE is not related to that library. This may or may not be a macport issue, but as you say, having both macported and OSX versions of Python may be causing a conflict. Please explain how I may follow your initial advise on removing manually-installed software it may help. Install py27-tkinter and IDLE installed by MacPorts python will work. (At least it opens for me when I did only that. I didn’t actually do anything in IDLE.) Lenore ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: help! - Python, Tkinter and IDLE
I don't have Python installed in the location /usr/local, and it isn't clear which Library you are referring to. I do not believe I told you as you claim, 'And you told us you installed Tcl and Tk in /Library/Frameworks. So that could be a problem.' As I have not ported Tcl/Tk, that cannot be the problem. AFAIK to run IDLE Python requires Tcl/tk. It was perhaps a long shot, but you may have helped rule out a possible cause of the problem being due to having both MacPorts and Apple-provided versions of Python installed. Thanks -A -Original Message- From: Ryan Schmidt To: uga...@talktalk.net CC: MacPorts Users Sent: Fri, 4 Apr 2014 11:46 Subject: Re: help! - Python, Tkinter and IDLE On Apr 4, 2014, at 05:17, uga...@talktalk.net wrote: > This is a follow up, I had originally posted in regard to problems running > the Tkinter libraries on a Macports installed version of Python. As a short term solution I reverted back to the OSX Python version, and I am now in the merde. > > Recently Ryan, wrote: > > "Software installed in /usr/local or /Library/Frameworks often causes > problems for MacPorts-installed software. You should use MacPorts, or manually-installed software in those locations, not both together; to avoid problems, please uninstall the one you don’t want to use." > > This is a bit unclear as there are several Library locations, and because Python on OSX v10.6.8 is located here: /System/Library/Frameworks/Python.framework/Versions/. . . I don’t doubt that, and there’s nothing wrong with that. > and I have nothing in /usr/local. In addition, the Macports Python installed here: /opt/local/Library/Frameworks/Python.framework/Versions/. . . I’m not disputing that. Re-read what I wrote. Software installed in the locations /usr/local or /Library/Frameworks is a problem. And you told us you installed Tcl and Tk in /Library/Frameworks. So that could be a problem. > I almost spoke to soon, when I was about to say: 'I am able to run either versions quite happily, and do not run the two versions at the same time'. I can continue to run either Python version happily but with a few exceptions. I still can't run IDLE with the macports version of Python (I have not yet ported Tcl/tk), but it did run with the OSX python version, until now that is. The problem is not running them at the same time. The problem is that the existence of software in /usr/local or /Library/Frameworks could be detected by software you’re trying to build with MacPorts, thereby either causing the build to fail, or causing the build to use those libraries instead of the MacPorts versions of same that should have been used. > Thinking about your advice, I pondered whether this is the cause of a problem that I am now experiencing, and I looked at un-installing the macports version, but I have been unable to proceed with this. I am unable to uninstall python27 @2.7.6_0 primarily because I want to retain Fontforge which depends on it. I guess I could try uninstalling Fontforge and dependencies, but this would leave me without Fontforge and it may not resolve the current IDLE issue for OSX Python. Another, possible solution is to port Tcl/Tk and re-activate the port Python as default, but I am not confident this will not also inherit the current problem that I am experiencing with IDLE, and I would like to resolve this issue in the first instance. My advice refers to the collection of software as a whole. Either use software installed by MacPorts (and uninstall software installed in /usr/local or /Library/Frameworks), or use software installed in /usr/local or /Library/Frameworks (and uninstall MacPorts and all software installed with it). Mixing and matching will lead to problems. > I have attached a screen grab of the alert message which now appears when I try to run IDLE from OSX Python. The message box is itself frozen, and the OK button unresponsive. Eventually a shape the size of the IDLE window appears on screen as a blank white square, and I have to force quit, to quit the python launcher. > In addition, this is the console message that appears in Terminal: > Apples-iMac-4:scripts apple$ IDLE > 11:20:00 > Traceback (most recent call last): > File "", line 1, in > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/idlelib/run.py", > line 7, in > import threading > File > "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/threading.py", > line 14, in > from time import time as _time, sleep as _sleep > ImportError: cannot import name sleep What is this command “IDLE”? What does “which IDLE” say? “IDLE” is not installed by the python27 port. The python27 port installs “idle2.7”. Please try running “idle2.7”. > The console message has identical content to a message that I am also currently investigating, and which had caused me to try to launch IDLE at this time. This problem re
Re: Python and Tkinter
Curious too, as the lib-tk diretory installed here: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk I note larryv@ posted in reply "…I think you need to install py27-tkinter also."and that this seemed to work for johnsankey@, so I may try this, but as the Tkinter library is already installed, it seems an odd approach. If I can be patient I will wait a further response. I tried a fresh port of python27, which seems only to have added a coppy of IDLE.app and Python Launcher.app in the Applications > MacPorts directory. Still no response from IDLE, and no Tkinter either. I have temporarily returned the default setting to OSX python v2.6.1 Tkinter seems to be installed for this version, but no IDLE. Many thanks. -A -Original Message- From: Lenore Horner To: MacPorts Users Sent: Wed, 2 Apr 2014 11:41 Subject: Re: Python and Tkinter > If you want to stick with MacPorts, then IDLE is already included with the python27 port, and tkinter is in the py27-tkinter port. If they don’t work, please report the bugs to us. It is included in the port, but is known not to work because IDLE depends in py27-tkinter which depends on python. See https://trac.macports.org/ticket/38746 https://trac.macports.org/ticket/42191 This defect was also discussed on this list back in January. Lenore Horner ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: Python and Tkinter
Ooops, I think should have included this here! -Original Message- From: uga...@talktalk.net To: ryandes...@macports.org Sent: Wed, 2 Apr 2014 10:55 Subject: Re: Python and Tkinter Thanks for the reply. I would like to stay with Macports but, Tkinter does not run, this is the traceback: >>> import Tkinter Traceback (most recent call last): File "", line 1, in File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk/Tkinter.py", line 39, in import _tkinter # If this fails your Python may not be configured for Tk ImportError: No module named _tkinter >>> It is unclear what steps need to be taken by me, to configure Python, but as you say it is included. I found it here in fact: /opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/lib-tk IDLE.app also fails to run. Yes, I believe I was invited to run python 2.7 as default. I am unable to report this as a bug as I do not know my login password. However, I hope this will be sufficient. In the meantime; what to do? Thanks -A -Original Message- From: Ryan Schmidt To: uga...@talktalk.net CC: MacPorts Users Sent: Wed, 2 Apr 2014 3:40 Subject: Re: Python and Tkinter On Apr 1, 2014, at 19:15, uga...@talktalk.net wrote: > I run OSX v10.6.8 (Snow Leopard) and I have a few versions of Python installed. The latest version is 2.7.6 installed itself along with (I beleive) a Macport installation of Fontforge. Being a Macport installation it is not located in the usual System > Library > . . . location. Nonetheless, if I run Terminal in interactive Python mode, this is the (default) version launched. Presumably because at some time you requested for that to happen, by running: sudo port select python python27 If you want to return to the OS X version of python being default, you would run: sudo port select python none > I do not seem to be able to launch IDLE, but more importantly to me, is that > I wish to install TKinter. I have downloaded the installer from ActiveState but I have not run it (at the time of writing). This is what the Read Me file states: > • ActiveTcl 8.5.15.1.297588 installs > • Tcl as a framework in > "/Library/Frameworks/Tcl.framework/Versions/8.5". > • Tk as a framework in > "/Library/Frameworks/Tk.framework/Versions/8.5". > • the packages in "/Library/Tcl/". > • Symbolic links and stubs are created in "/usr/local/bin" for > launching tclsh, and wish from the command line. > • Symbolic links are created in "/Applications/Utilities" for launching > wish from the Finder, Panel, etc. > • The ActiveTcl documentation is installed in the Tcl framework, but a symbolic link is created in "/Library/Documentation/Help/ActiveTcl-8.5" to them. > The question is; should I proceed with the ActiveState installation, or is their a better alternative Port option? > > I am concerned that the location of Python v2.7.6 which is located in /opt/local/Library/Frameworks/Python.framework/Versions/2.7 may be on issue. Software installed in /usr/local or /Library/Frameworks often causes problems for MacPorts-installed software. You should use MacPorts, or manually-installed software in those locations, not both together; to avoid problems, please uninstall the one you don’t want to use. If you want to stick with MacPorts, then IDLE is already included with the python27 port, and tkinter is in the py27-tkinter port. If they don’t work, please report the bugs to us. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Python and Tkinter
I run OSX v10.6.8 (Snow Leopard) and I have a few versions of Python installed. The latest version is 2.7.6 installed itself along with (I beleive) a Macport installation of Fontforge. Being a Macport installation it is not located in the usual System > Library > . . . location. Nonetheless, if I run Terminal in interactive Python mode, this is the (default) version launched. I do not seem to be able to launch IDLE, but more importantly to me, is that I wish to install TKinter. I have downloaded the installer from ActiveState but I have not run it (at the time of writing). This is what the Read Me file states: ActiveTcl 8.5.15.1.297588 installs Tcl as a framework in "/Library/Frameworks/Tcl.framework/Versions/8.5". Tk as a framework in "/Library/Frameworks/Tk.framework/Versions/8.5". the packages in "/Library/Tcl/". Symbolic links and stubs are created in"/usr/local/bin" for launching tclsh,and wish from the command line. Symbolic links are created in"/Applications/Utilities" for launching wish from the Finder, Panel, etc. The ActiveTcl documentation is installed in the Tclframework, but a symbolic link is created in"/Library/Documentation/Help/ActiveTcl-8.5" to them. The question is; should I proceed with the ActiveState installation, or is their a better alternative Port option? I am concerned that the location of Python v2.7.6 which is located in /opt/local/Library/Frameworks/Python.framework/Versions/2.7 may be on issue. Many thanks. -A ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: fontforge - port installation
Much appreciated and interesting. Files were installed into /usr/local Deleting them was very satisfying. Thanks. -A -Original Message- From: Ryan Schmidt To: uga...@talktalk.net CC: MacPorts Users Sent: Tue, 5 Nov 2013 19:40 Subject: Re: fontforge - port installation On Nov 5, 2013, at 06:03, uga...@talktalk.net wrote: > It is unclear where to get more detailed and specific info for the variants, so I guess I will go with the default. > fontforge has the variants: >freetype_bytecode: Enable support for bytecode interpreter fontforge uses the freetype library. The freetype library has a feature called the bytecode interpreter which lets it display glyphs more accurately, but the method it uses to do so was covered by an Apple Inc patent, so the freetype project was not legally allowed to use that method. The freetype port had variant allowing users (in regions of the world not covered by that patent) to use the feature anyway. The patent expired in 2010 so everybody may now legally use it. The freetype port now always uses the bytecode interpreter; the variant has been deleted. The fontforge port has not had a maintainer since 2006 (r18094) so I guess nobody has noticed that fontforge still has this variant. Perhaps we should remove the variant from fontforge and always enable the feature there too. It’s also possible that the changes in freetype to always enable this feature will make fontforge unable to use this feature. The developers of fontforge appear not to have noticed the expiration of this patent either, since the latest code in their repository still refers users to Apple to get a license for the expired patent. I will attempt to report that problem to the developers of fontforge. If you’re interested, this page shows the difference using the bytecode interpreter makes: http://www.ludd.luth.se/~staham/linux/bci.shtml >python26: Enable Python support (Python 2.6) > * conflicts with python27 >python27: Enable Python support (Python 2.7) > * conflicts with python26 Select one of these variants if you want python support in fontforge. I don’t know what that entails. In fact the port seems to be somewhat confused: it looks like the port actually includes python27 support, even if you don’t select either of these variants. This is a bug in the port that should be fixed. >universal: Build for multiple architectures Instead of building for only your machine’s normal architecture, the universal variant builds a port for multiple architectures. Most ports have universal variants, but most users don’t usually need it. It’s needed if you want to build a port on one computer and then run it on a second computer that has a different processor. Perhaps you want to build a standalone installer package for this port that you can distribute to other users. MacPorts will automatically select the universal variant if it’s needed. For example, if you are using a 64-bit Mac, and the port you’re trying to install is only available 32-bit, but has dependencies on other ports that can be built 64-bit, then MacPorts will install those dependencies with the universal variant in order to build them for both 32-bit and 64-bit. >with_freetype_bytecode: Legacy compatibility variant > * requires freetype_bytecode Legacy compatibility variants are not of interest to new users. We keep these around for a year or so to help users who already installed a previous version of the port upgrade to a new version. Since this variant had already been around for 2 years, I have now deleted it. > Will it matter if I fail to uninstall any of the dependencies for the the current (non-working) pkg version of fontforge? I don’t know where your previous non-MacPorts fontforge installed its files. If, for example, it installed files, especially libraries, into /usr/local, then yes, that could be a problem. You should uninstall it, but most Mac software packages do not come with an uninstallation program, so you’ll have to check the web site where you got that installer package to see if they have any uninstallation instructions. Or you can re-download their installer, open it, don’t install it, but instead use the Show Files command in the Installer's File menu to see what it would install, then manually find those files on your drive and delete them. Ease of uninstallation is one of the reasons why installing software with MacPorts is so much more convenient… ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: fontforge - port installation
Yes fontforge has the variants: freetype_bytecode: Enable support for bytecode interpreter python26: Enable Python support (Python 2.6) * conflicts with python27 python27: Enable Python support (Python 2.7) * conflicts with python26 universal: Build for multiple architectures with_freetype_bytecode: Legacy compatibility variant * requires freetype_bytecode The above was included in an earlier post. I guess I may or may not find out, if I fail first to uninstall any of the dependencies for the the current (non-working) pkg version of fontforge. -A -Original Message- From: Chris Jones To: MacPorts Users Sent: Tue, 5 Nov 2013 13:11 Subject: Re: fontforge - port installation It is unclear where to get more detailed and specific info for the variants, so I guess I will go with the default. > port variants fontforge ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: fontforge - port installation
Thanks It is unclear where to get more detailed and specific info for the variants, so I guess I will go with the default. Will it matter if I fail to uninstall any of the dependencies for the the current (non-working) pkg version of fontforge? -A -Original Message- From: Ryan Schmidt To: uga...@talktalk.net CC: Jeremy Lavergne ; MacPorts Users Sent: Mon, 4 Nov 2013 21:23 Subject: Re: fontforge - port installation On Nov 4, 2013, at 09:40, uga...@talktalk.net wrote: > I think it was a misguided example, > "sudo port install fontforge" > > > > will do? If you do not want any of the offered variants, then yes, that will do. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: fontforge - port installation
I think it was a misguided example, "sudo port install fontforge" will do? -A -Original Message- From: Jeremy Lavergne To: uga...@talktalk.net CC: MacPorts Users Sent: Mon, 4 Nov 2013 15:32 Subject: Re: fontforge - port installation `port variants`, which you ran, shows the variants as they’d be chosen for the command. Since there are no + or - shown, no variants will be chosen or disabled by default. You can always be explicit about your variants, even if they’re defaults: sudo port PORTNAME -thing +other Are you sure you need +universal? or was it just an example? For a universal binary of fontforge: sudo port install fontforge +universal On Nov 4, 2013, at 9:51, uga...@talktalk.net wrote: > Assuming I wish to install the universal variant is > "sudo port install fontforge" the correct instruction, and/or > do I need to invoke or negate any variants? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
fontforge - port installation
I have an old version of fontforge, which was installed using a pkg installer. It had been been working fine, but now crashes during start-up. I can't think what I may have changed to cause this, save that I recently installed Macports and completed a MyPaint port. In any event, I am considering trying a fresh port installation of fontforge. Do I need to uninstall the current (non-working) version of fontforge? How do I decide which variant to install? fontforge has the variants: freetype_bytecode: Enable support for bytecode interpreter python26: Enable Python support (Python 2.6) * conflicts with python27 python27: Enable Python support (Python 2.7) * conflicts with python26 universal: Build for multiple architectures with_freetype_bytecode: Legacy compatibility variant * requires freetype_bytecode Assuming I wish to install the universal variant is "sudo port install fontforge" the correct instruction, and/or do I need to invoke or negate any variants? Many thanks. -A ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: macports instal pkg - alert msg
Yup, there is so much that I do not understand. The discussion about directories is relevant to me, as I wish to understand and I must decide which installation I should keep. Thanks for your help. -Original Message- From: Sterling Smith To: uga...@talktalk.net CC: macports-users@lists.macosforge.org Sent: Fri, 11 Oct 2013 15:25 Subject: Re: macports instal pkg - alert msg A, Perhaps you don't understand what macports is. It is a way of installing various applications (or libraries), with the correct understanding and installation of the dependencies for that application. The usual way of installing a given application is to find out its portname > port search mypaint MyPaint @1.1.0_1 (graphics) a fast and easy graphics application for digital painters Then find out if you need a particular variant >port variants MyPaint MyPaint has the variants: universal: Build for multiple architectures No unusual variants for MyPaint, so proceed with installation. >sudo port install MyPaint After that installs successfully, start a new terminal session so that your path is up to date. Then to find the command that you need to run on the command line, look at the output of >port contents MyPaint | grep bin or >port contents MyPaint | grep -i .app If there is a newer version of MyPaint than 1.1.0, then file a bug report requesting an update.[1,2] The discussion about using different directories (/opt/local, etc.) is not relevant unless you are trying to create the .pkg to be redistributed to others. Hope that helps, Sterling [1] http://guide.macports.org/#project.tickets.creating [2] https://trac.macports.org/newticket On Oct 11, 2013, at 6:46AM, uga...@talktalk.net wrote: > Thanks. > > What is normal to you? > > I don't recall using a prefix, but ran both installers from their default location which happened to be /opt/local, > also I did not choose /Applications/MacPorts as applications_dir to create > the package in the first place. > Both installs were left at default setting. > > It seems I now have a decision to make and some files to delete. > > I don't want to distribute, but there is no Mac pkg available for this (latest) version of mypaint. As the earlier version has serious > functional deficits (no pressure sensitivity) I am glad to make it available. However, I am not sure how or where to do this. I have > posted a note on a mypaint forum. Perhaps someone will tell me. > > Thanks again to you, all. > > -A > > > > > -Original Message- > From: Rainer Müller > To: macports-users@lists.macosforge.org > Sent: Fri, 11 Oct 2013 13:32 > Subject: Re: Fwd: macports instal pkg - alert msg > > On 2013-10-11 12:22, uga...@talktalk.net > wrote: > > I have completed first 'successful' MacPorts instal, but something seems > > not to be quite right. > > > > What have I done, and how do I put it right? > > > > Following the MacPorts guide, I ran (and I am not sure I needed to do > > this); sudo port pkg mypaint > > Creating a pkg is only necessary if you want to redistribute this > package. Otherwise just use a normal installation: > > sudo port install mypaint > > > In case you really want to redistribute this package, you should not use > /opt/local as prefix and /Applications/MacPorts as applications_dir to > create the package in the first place. Please choose a different prefix > to avoid conflicts. > > > [...] > > I seem to have a duplicate tree structure within destroot. Is this as it > > should be? I now have; > > HD/opt/local/var/macports/build/ _opt_local_var_macports. . . > > /MyPaint/work/destroot/opt/ . . (see above) > > and; > > HD/opt/local/var/macports/build/ _opt_local_var_macports. . . > > /MyPaint/work/destroot/Applications/MacPorts/MyPaint.app > > This looks correct. > > > A further MyPaint.app is located. HD/Applications/MacPorts/MyPaint.pp > > This is the installed version from the pkg installer. > > > Previously, I had installed an earlier release of MyPaint using a pkg > > installer and this located the directories (bin, include, lib, & share) > > listed above in destroot/ directly in HD/opt/ directory. > > Then it was probably not created by a default MacPorts installation, > which uses /opt/local. > > Rainer > ___ > macports-users mailing list > > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users > ___ > macports-users mailing list > macports-users@lists.macosforge.org > https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: macports instal pkg - alert msg
Thanks. What is normal to you? I don't recall using a prefix, but ran both installers from their default location which happened to be /opt/local, also I did not choose /Applications/MacPorts as applications_dir tocreate the package in the first place. Both installs were left at default setting. It seems I now have a decision to make and some files to delete. I don't want to distribute, but there is no Mac pkg available for this (latest) version of mypaint. As the earlier version has serious functional deficits (no pressure sensitivity) I am glad to make it available. However, I am not sure how or where to do this. I have posted a note on a mypaint forum. Perhaps someone will tell me. Thanks again to you, all. -A -Original Message- From: Rainer Müller To: macports-users@lists.macosforge.org Sent: Fri, 11 Oct 2013 13:32 Subject: Re: Fwd: macports instal pkg - alert msg On 2013-10-11 12:22, uga...@talktalk.net wrote: > I have completed first 'successful' MacPorts instal, but something seems > not to be quite right. > > What have I done, and how do I put it right? > > Following the MacPorts guide, I ran (and I am not sure I needed to do > this); sudo port pkg mypaint Creating a pkg is only necessary if you want to redistribute this package. Otherwise just use a normal installation: sudo port install mypaint In case you really want to redistribute this package, you should not use /opt/local as prefix and /Applications/MacPorts as applications_dir to create the package in the first place. Please choose a different prefix to avoid conflicts. > [...] > I seem to have a duplicate tree structure within destroot. Is this as it > should be? I now have; > HD/opt/local/var/macports/build/ _opt_local_var_macports. . . > /MyPaint/work/destroot/opt/ . . (see above) > and; > HD/opt/local/var/macports/build/ _opt_local_var_macports. . . > /MyPaint/work/destroot/Applications/MacPorts/MyPaint.app This looks correct. > A further MyPaint.app is located. HD/Applications/MacPorts/MyPaint.pp This is the installed version from the pkg installer. > Previously, I had installed an earlier release of MyPaint using a pkg > installer and this located the directories (bin, include, lib, & share) > listed above in destroot/ directly in HD/opt/ directory. Then it was probably not created by a default MacPorts installation, which uses /opt/local. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: macports instal pkg - alert msg
I have completed first 'successful' MacPorts instal, but something seems not to be quite right. What have I done, and how do I put it right? Following the MacPorts guide, I ran (and I am not sure I needed to do this); sudo port pkg mypaint In opt/local/var/macports/build/ _opt_local_var_macports. . . /MyPaint/work/ I have (excluding hidden files) two pkg files, MyPaint-1.1.0_1.pkg and MyPaint-1.1.0_1-component.pkg together with a folder named destroot I ran both installers (should I have done this?). Both installed to the same destination and were reported as successful. MyPaint-1.1.0_1.pkg runs the MacPorts MyPaint installer and MyPaint-1.1.0_1-component.pkg runs the default apple installer The folder destroot has two sub-folders; destroot/Applications/MacPorts/MyPaint.app destroot/opt/local/bin/ destroot/opt/local/include/ destroot/opt/local/bin/lib/ destroot/opt/local/bin/share/ I seem to have a duplicate tree structure within destroot. Is this as it should be? I now have; HD/opt/local/var/macports/build/ _opt_local_var_macports. . . /MyPaint/work/destroot/opt/ . . (see above) and; HD/opt/local/var/macports/build/ _opt_local_var_macports. . . /MyPaint/work/destroot/Applications/MacPorts/MyPaint.app A further MyPaint.app is located. HD/Applications/MacPorts/MyPaint.pp Previously, I had installed an earlier release of MyPaint using a pkg installer and this located the directories (bin, include, lib, & share) listed above in destroot/ directly in HD/opt/ directory. Many thanks, again. -A -Original Message- From: Monti Coburn To: uga...@talktalk.net Sent: Fri, 11 Oct 2013 4:09 Subject: Re: Fwd: macports instal pkg - alert msg :-) On Oct 10, 2013 9:40 PM, wrote: Got it now, I think :) Thanks, again. -Original Message- From: uga...@talktalk.net To: ctrelea...@cogeco.ca Sent: Fri, 11 Oct 2013 3:05 Subject: Re: macports instal pkg - alert msg I also have the the Xcode.app v3.2.6 (included with Xcode developer tools) installed. Thanks -A -Original Message- From: Craig Treleaven To: uga...@talktalk.net; macports-users@lists.macosforge.org Sent: Fri, 11 Oct 2013 1:54 Subject: Re: macports instal pkg - alert msg At 8:49 PM -0400 10/10/13, uga...@talktalk.net wrote: >On running the MacPorts 2.2.0 for Mac OSX installer (I am running >OSX >v10.6.8) I get an alert msg which reads; Xcode is not installed, >or was >installed without UNIX Development > >I have been alerted, but the msg isn't clear, which is alarming. Do >I need to >do something before continuing to instal Macports? > >X11 is installed - I am assuming Xcode means X11 and not Xcode.app - >In point >of fact I have two versions of X11 installed, XQuartz 2.7.4 >(xorg-server >1.13.0) and XQuartz 2.3.6 (xorg-server 1.4.2-apple56). >I hope this helps. No, XCode is Apple's integrated development environment. MacPorts cannot function without it. Check the docs again: http://www.macports.org/install.php Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Fwd: macports instal pkg - alert msg
Got it now, I think :) Thanks, again. -Original Message- From: uga...@talktalk.net To: ctrelea...@cogeco.ca Sent: Fri, 11 Oct 2013 3:05 Subject: Re: macports instal pkg - alert msg I also have the the Xcode.app v3.2.6 (included with Xcode developer tools) installed. Thanks -A -Original Message- From: Craig Treleaven To: uga...@talktalk.net; macports-users@lists.macosforge.org Sent: Fri, 11 Oct 2013 1:54 Subject: Re: macports instal pkg - alert msg At 8:49 PM -0400 10/10/13, uga...@talktalk.net wrote: >On running the MacPorts 2.2.0 for Mac OSX installer (I am running >OSX >v10.6.8) I get an alert msg which reads; Xcode is not installed, >or was >installed without UNIX Development > >I have been alerted, but the msg isn't clear, which is alarming. Do >I need to >do something before continuing to instal Macports? > >X11 is installed - I am assuming Xcode means X11 and not Xcode.app - >In point >of fact I have two versions of X11 installed, XQuartz 2.7.4 >(xorg-server >1.13.0) and XQuartz 2.3.6 (xorg-server 1.4.2-apple56). >I hope this helps. No, XCode is Apple's integrated development environment. MacPorts cannot function without it. Check the docs again: http://www.macports.org/install.php Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
macports instal pkg - alert msg
On running the MacPorts 2.2.0 for Mac OSX installer (I am running OSX v10.6.8) I get an alert msg which reads; Xcode is not installed, or was installed without UNIX Development I have been alerted, but the msg isn't clear, which is alarming. Do I need to do something before continuing to instal Macports? X11 is installed - I am assuming Xcode means X11 and not Xcode.app - In point of fact I have two versions of X11 installed, XQuartz 2.7.4 (xorg-server 1.13.0) and XQuartz 2.3.6 (xorg-server 1.4.2-apple56). I hope this helps. Many thanks in anticipation . -A ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
