Re: MacPorts Statistics (was Re: usage numbers for macports vs. homebrew?)
On 19 Mar 2014, at 21:03 , Jeremy Lavergne jer...@lavergne.gotdns.org wrote: From what I can see, our tool will not gather whether a port was Requested or not. I think that's a key data point. Some libs will get installed very frequently as dependencies but will seldom be requested. At the time of GSoC11, I don’t think MacPorts even had the notion of requested ports. Nothing prevents this from being added at any later date. Counting requested ports seems a better approach to it, but is certainly very much privacy related. One has to add that only by focusing on requested ports all the statistics graphs make much more sense. Otherwise one would see - as now - only the very basic ports being shown in the stats as most installed ports. This is certainly also vital information, but perhaps one could have switch to toggle the viewpoint between all ports and only considering requested ones. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
osxutils
Recently updated from Lion to Mavericks; updated most of my stuff, a few didn't work, and mostly weren't anything I cared about; since I did that in part to also update BootCamp so I could use update my Windows partition from 8 to 8.1, on top of having all the other apps and stuff that needed updating for 10.9, I had a very full day when I did that. I think I kept notes, so if anyone is interested, I could dig up the ones that didn't build, although I suspect most are probably known by now. Probably unrelated however, I ran across a case where I wanted some of the osxutils commands (mkalias in particular). I'd had an old non-packaged build of them, but they were ppc, so they must've become useless when Rosetta went away on my older system. Haven't wanted them often apparently, but very much so when I did. :-) Naturally I tried the MacPorts port, but it didn't work. But some googling found me that someone else has been keeping them up-to-date enough that theirs still builds on 10.9.2! I have no idea if it builds on versions as far back as you want to support, though. https://github.com/vasi/osxutils Being impatient, rather than fiddle with git, I just grabbed the zip file, did cd ~/Downloads/osxutils-master # zip file was automatically unzipped on download make and it all built. I suppose depending on whether it will build on the earliest OS X version MacPorts intends to support, it might either be possible to adopt this version in its entirety, or else merge it in such a way (#ifdef's?) as to work on all versions. I have neither the time nor the experience with Mac-specific software building quirks to pursue that myself, but for whoever (if anyone is maintaining the MacPorts port of osxutils, I thought they might find this interesting. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: osxutils
Hmm, the osxutils port is unmaintained… Perhaps someone might pick it up, now that you could verify that it is running fine in its current version (1.8.1 i suppose). :-) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: osxutils
I can verify that what I downloaded from https://github.com/vasi/osxutils would build cleanly (as of the state of the code when I downloaded it). The code does not include a test suite, so I can only verify that mkalias appeared to work as expected in the particular way I used it (the structure of the alias file seemed to be what one might expect at a very quick glance, and Finder handled it properly). I can try running those of the other commands that are reasonably non-disruptive, but that's a far cry from verify that it is running fine. Not that I think there's likely to be much ongoing maintenance needed (except when OS library or header file features that the code uses are deprecated or the like), just that there's a difference between building and running. :-) On Mar 20, 2014, at 3:48 AM, mk-macpo...@techno.ms wrote: Hmm, the osxutils port is unmaintained… Perhaps someone might pick it up, now that you could verify that it is running fine in its current version (1.8.1 i suppose). :-) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users -- eMail: mailto:rlha...@smart.net Home page: http://www.smart.net/~rlhamil/ Facebook, MySpace, AIM, Yahoo, etc:ask ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts Statistics (was Re: usage numbers for macports vs. homebrew?)
Hi Craig, Thanks, that helped a lot. I like the page layout, very clean. I have to say, though that I'm not a big fan of pie (or donut) graphs. It is much easy to compare magnitudes of a bar as opposed to sections of a donut. I agree. Patches welcome. In general, if anybody with a little more knowledge and experience than me in Ruby on Rails wants to improve this, the code is linked on the site and patches are welcome. For example, it currently doesn't trac the inactive ports (even though they are submitted). As a port maintainer, one key thing I'd like to know is the breakdown of OS versions that my users are running. The data is available for that, right? Just a matter of extracting and presenting it? Yes, that data is available. I think all the graphs need to be given a little thought. If somebody has the time to make a list of graphs that might be useful given the data we have, feel free to make a wiki page for that or even just reply to that email. Anything helps :) One other minor observation: what is the GCC Version supposed to represent? http://stats.macports.neverpanic.de/os_statistics#gcc_version If we know the XCode version that the user has installed, we'll already know the default compilers available on that system. Not necessarily. The correct thing to track would be the version of the Command Line Tools. The GCC version tracking should be removed, it's pointless on modern OS X. Seriously though, it says to install the mpstats port, but port cannot find anything by that name. Even searching for “stat” doesn’t seem to show any likely candidates. That's correct. The port currently doesn't work on any released version of MacPorts (it requires 2.3) and hasn't been committed to the main repository for that reason. If you're running trunk you can get it using sudo port install http://files.neverpanic.de/mpvim.tar. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [117551] trunk/dports/multimedia/x264/Portfile
At 8:48 AM -0800 3/3/14, dev...@macports.org wrote: Revision https://trac.macports.org/changeset/117551117551 Author dev...@macports.org Date 2014-03-03 08:48:17 -0800 (Mon, 03 Mar 2014) Log Message x264: update to build 142, make +asm default for x86_64, SL and up. [...] WOW! I presume it was the assembler optimizations that made gave this a big speed boost: from 12-16 fps to ~55 fps!! Same source and destination formats. Can now transcode ATSC OTA to an iPad-compatible format faster than real time. Very big thanks. Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [117551] trunk/dports/multimedia/x264/Portfile
On 3/20/14 8:55 AM, Craig Treleaven wrote: At 8:48 AM -0800 3/3/14, dev...@macports.org wrote: Revision https://trac.macports.org/changeset/117551117551 Author dev...@macports.org Date 2014-03-03 08:48:17 -0800 (Mon, 03 Mar 2014) Log Message x264: update to build 142, make +asm default for x86_64, SL and up. [...] WOW! I presume it was the assembler optimizations that made gave this a big speed boost: from 12-16 fps to ~55 fps!! Same source and destination formats. Can now transcode ATSC OTA to an iPad-compatible format faster than real time. Very big thanks. Craig Great! Thanks for the benchmark report and testimonial. Dave ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [117551] trunk/dports/multimedia/x264/Portfile
Hi, WOW! I presume it was the assembler optimizations that made gave this a big speed boost: from 12-16 fps to ~55 fps!! Same source and destination formats. Might also have been http://trac.macports.org/changeset/117917 if you use ffmpeg. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: eigen
Hello, More generally, it is also possible to use eigen3 in compatibility mode, which works for most modules. I could use this for example in Kstars to keep to the port to build. I'll have a look at that, but I prefer to have the maximum of optional components available. I started out trying to build without GLEW, but realised rather quickly that the code hadn't been tested for a while in its absence. And in fact, the only true issue I had until now was probably introduced by (or was at least concurrent with) not building the gmic extension for Krita. I may have expressed myself incorrectly, but the compatibility mode of eigen3 does not reduce the amount of options of calligra. It provides full support, apart from some modules which are not supported. It is thus a yes/no case, where either you can use the compatibility mode if you are not using the unsupported modules, or you have to adjust your code. For what I tested in the past with Calligra’s Portfile, it is possible to use the compatibility mode. [snip] but the applications I tested seemed functional enough. The suite is well too complicated to assert if it's completely working, aside from what the unit tests say… Well, if you get something which is working satisfyingly, I would encourage you to attach your Portfile to the ticket #37579. Calligra is still not an official port of Macports, so if there is something working, it would be nice to have it committed. Cheers, Nicolas ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts 2.3.0-beta1 now available for testing
Source code and pkgs for MacPorts 2.3.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There are a large number of changes in this release. See the ChangeLog [4] for a list of most of them. You may like to focus your testing on the new features in that list, as well as your normal usage. Cheers, Josh [1] https://distfiles.macports.org/MacPorts/testing/ [2] https://trac.macports.org/newticket [3] https://trac.macports.org/search [4] https://trac.macports.org/browser/branches/release_2_3/base/ChangeLog ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: [117551] trunk/dports/multimedia/x264/Portfile
At 5:16 PM +0100 3/20/14, Clemens Lang wrote: Hi, WOW! I presume it was the assembler optimizations that made gave this a big speed boost: from 12-16 fps to ~55 fps!! Same source and destination formats. Might also have been http://trac.macports.org/changeset/117917 if you use ffmpeg. Nope, this is with mythtv-core.27. Besides, VDA is Video _Decode_ Acceleration, no? Wouldn't have an impact on re-encoding from MPEG2 to H264, I don't think. Craig ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts Statistics (was Re: usage numbers for macports vs. homebrew?)
On Thu, Mar 20, 2014 at 11:54 AM, Clemens Lang wrote: Seriously though, it says to install the mpstats port, but port cannot find anything by that name. Even searching for “stat” doesn’t seem to show any likely candidates. That's correct. The port currently doesn't work on any released version of MacPorts (it requires 2.3) and hasn't been committed to the main repository for that reason. If you're running trunk you can get it using sudo port install http://files.neverpanic.de/mpvim.tar. In what way is mpvim related to mpstats? Mojca ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
tcptraceroute
Any chance we could get tcptraceroute ported? -brad ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: osxutils
On Mar 20, 2014, at 02:48, mk-macpo...@techno.ms wrote: Perhaps someone might pick it up, now that you could verify that it is running fine in its current version (1.8.1 i suppose). :-) Done: https://trac.macports.org/changeset/118064 Thanks for letting us know about this, Richard. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: tcptraceroute
On Mar 20, 2014, at 13:35, Brad Allison wrote: Any chance we could get tcptraceroute ported? The tcptraceroute port has already existed for 10 years. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
gnuplot
Dear users, I am trying to install the port gnuplot on my macbook air with OS X 10.9.2 with the command sudo port install gnuplot I obtain the following error message: --- Computing dependencies for libpng --- Extracting libpng Error: org.macports.extract for port libpng returned: command execution failed Please see the log file for port libpng for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpng/libpng/main.log Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade fontconfig failed how can i solve it? thanks Gaetano ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnuplot
On Thu, Mar 20, 2014 at 3:12 PM, Gaetano Sardina gaetano...@gmail.comwrote: sudo port install gnuplot I obtain the following error message: --- Computing dependencies for libpng --- Extracting libpng Error: org.macports.extract for port libpng returned: command execution failed Please see the log file for port libpng for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpng/libpng/main.log Could you please provide the contents of the above named file? -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts Statistics (was Re: usage numbers for macports vs. homebrew?)
Hi, sudo port install http://files.neverpanic.de/mpvim.tar. In what way is mpvim related to mpstats? In none, I'm sorry. Correct URL is https://neverpanic.de/documents/mpstats.tar -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnuplot
Hi, Dear users, I am trying to install the port gnuplot on my macbook air with OS X 10.9.2 with the command sudo port install gnuplot I obtain the following error message: --- Computing dependencies for libpng --- Extracting libpng Error: org.macports.extract for port libpng returned: command execution failed Please see the log file for port libpng for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_graphics_libpng/libpng/main.log Error: Unable to upgrade port: 1 Error: Unable to execute port: upgrade fontconfig failed Did you recently upgrade to Mavericks? If so, read https://trac.macports.org/wiki/MavericksProblems and https://trac.macports.org/wiki/Migration. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
MacPorts automake and python
Hi Since automake was bumped to 1.14.1_1 it can't be used to build any python software outside of MacPorts as it always tries to install the python modules into MacPorts prefix. I understand why we want to ensure that ports always installs modules into the MacPorts prefix, but I can't understand why we would force this for everything using MacPorts python. When I questioned this I was told that I should be using a non MacPorts python if I don't want the modules to end up in the MacPorts prefix? If that is the case what's the point of MacPorts? I was under the impression that the goal of the project was to provide an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the OS X operating system. But now I'm getting told that I shouldn't be using MacPorts but I should be installing things locally if I don't want to install modules into the MacPorts prefix. This change seems like a very bad idea and is surely going to cause problems down the line, in fact at work several users have already been bitten by this. Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
Isn’t this a pythonism, things install to python’s site-packages directory? On Mar 20, 2014, at 15:25, Adam Mercer r...@macports.org wrote: Since automake was bumped to 1.14.1_1 it can't be used to build any python software outside of MacPorts as it always tries to install the python modules into MacPorts prefix. I understand why we want to ensure that ports always installs modules into the MacPorts prefix, but I can't understand why we would force this for everything using MacPorts python. When I questioned this I was told that I should be using a non MacPorts python if I don't want the modules to end up in the MacPorts prefix? If that is the case what's the point of MacPorts? I was under the impression that the goal of the project was to provide an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the OS X operating system. But now I'm getting told that I shouldn't be using MacPorts but I should be installing things locally if I don't want to install modules into the MacPorts prefix. This change seems like a very bad idea and is surely going to cause problems down the line, in fact at work several users have already been bitten by this. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Isn't this a pythonism, things install to python's site-packages directory? The main point is that we don't want random things, outside the control of MacPorts, installed in the MacPorts prefix. This is just going to lead to people forcing an install, with sudo for example, and overwriting something from MacPorts and then leading to breakage. Cheers Adam ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
Adam Mercer r...@macports.org writes: Hi Since automake was bumped to 1.14.1_1 it can't be used to build any python software outside of MacPorts as it always tries to install the python modules into MacPorts prefix. I understand why we want to ensure that ports always installs modules into the MacPorts prefix, but I can't understand why we would force this for everything using MacPorts python. When I questioned this I was told that I should be using a non MacPorts python if I don't want the modules to end up in the MacPorts prefix? If that is the case what's the point of MacPorts? I was under the impression that the goal of the project was to provide an easy-to-use system for compiling, installing, and upgrading either command-line, X11 or Aqua based open-source software on the OS X operating system. But now I'm getting told that I shouldn't be using MacPorts but I should be installing things locally if I don't want to install modules into the MacPorts prefix. This change seems like a very bad idea and is surely going to cause problems down the line, in fact at work several users have already been bitten by this. I tend to agree with you but need help seeing how this worked before. What path did automake pick up before this change? ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
On Mar 20, 2014, at 3:50 PM, Adam Mercer r...@macports.org wrote: On Thu, Mar 20, 2014 at 2:28 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote: Isn't this a pythonism, things install to python's site-packages directory? The main point is that we don't want random things, outside the control of MacPorts, installed in the MacPorts prefix. This is just going to lead to people forcing an install, with sudo for example, and overwriting something from MacPorts and then leading to breakage. for perl, there's a 'vendor' directory (where we install stuff) and a 'site' directory (where anything goes). If an end-user installs his/her own perl modules, they end up in the site directory (which is in $prefix). Of course, things could be much better for perl than the way we're doing things now, so maybe it's not the best example... -- Daniel J. Luke ++ | * dl...@geeklair.net * | | *-- http://www.geeklair.net -* | ++ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | ++ ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley s...@macports.org wrote:
I tend to agree with you but need help seeing how this worked
before. What path did automake pick up before this change?
If you look at the patch you can see the original paths:
http://trac.macports.org/browser/trunk/dports/devel/automake/files/patch-m4-python.m4.diff
The original paths are:
AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
Just to clarify this isn't the MacPorts prefix but the prefix for the
running configure process.
Cheers
Adam
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
On Thu, Mar 20, 2014 at 4:27 PM, Daniel J. Luke dl...@geeklair.net wrote: for perl, there's a 'vendor' directory (where we install stuff) and a 'site' directory (where anything goes). If an end-user installs his/her own perl modules, they end up in the site directory (which is in $prefix). Of course, things could be much better for perl than the way we're doing things now, so maybe it's not the best example... That is how Perl normally works, though... and how, to be honest, I'd expect Python to behave. You need local configuration to change it. (Possibly Perl makes this easier than Python does, though; that'd be Python all over... One True Way instead of letting you configure it.) -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
Adam Mercer r...@macports.org writes:
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley s...@macports.org wrote:
I tend to agree with you but need help seeing how this worked
before. What path did automake pick up before this change?
If you look at the patch you can see the original paths:
http://trac.macports.org/browser/trunk/dports/devel/automake/files/patch-m4-python.m4.diff
The original paths are:
AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
Just to clarify this isn't the MacPorts prefix but the prefix for the
running configure process.
Right, sorry, I meant more along the lines of:
Before: my project installed into /path/foo/a
After: my project installed into /path/foo/b
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts automake and python
On Thu, Mar 20, 2014 at 9:47 PM, Adam Mercer wrote:
On Thu, Mar 20, 2014 at 2:55 PM, Sean Farley wrote:
I tend to agree with you but need help seeing how this worked
before. What path did automake pick up before this change?
If you look at the patch you can see the original paths:
http://trac.macports.org/browser/trunk/dports/devel/automake/files/patch-m4-python.m4.diff
The original paths are:
AC_SUBST([PYTHON_PREFIX], ['${prefix}'])
AC_SUBST([PYTHON_EXEC_PREFIX], ['${exec_prefix}'])
The way how I imagine it to work in a user-friendly way (variable
names and ways to achieve that may vary):
* MacPorts (or the Python PortGroup) always sets something equivalent to
export PYTHON_PREFIX=`$PYTHON -c import sys;
sys.stdout.write(sys.prefix);`
which takes precedence over defaults (in the same way as MacPorts
always sets LDFLAGS='-L/opt/local/lib...' or --prefix=/opt/local)
* User can always set PYTHON_PREFIX=/any/path and that setting is also
obeyed (takes priority over --prefix=...)
* In all other cases install to ${prefix} / ${exec_prefix} (as used to
be the case).
Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On 20 Mar 2014, at 20:19 , Clemens Lang c...@macports.org wrote: https://neverpanic.de/documents/mpstats.tar I installed the latest testing beta just OVER my stable MacPorts (keeping a copy of /opt/local put aside, of course): — $ port MacPorts 2.2.99 $ sudo port install https://neverpanic.de/documents/mpstats.tar . . . $ port installed mpstats The following ports are currently installed: mpstats @0.1.3_0 (active) $ port notes mpstats Error: The port 'mpstats' was not found — but as one can see MacPorts claims - when asking for the port's notes - that the port isn’t installed!!!? Also tab completion suddenly doesn’t work anymore… — $ port installed mpPRESSED TAB HERE mpfr mpvim — What’s going on here??? Perhaps I need to reboot? ;-) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On Mar 20, 2014, at 17:18, mk-macpo...@techno.ms wrote: On 20 Mar 2014, at 20:19 , Clemens Lang c...@macports.org wrote: https://neverpanic.de/documents/mpstats.tar I installed the latest testing beta just OVER my stable MacPorts (keeping a copy of /opt/local put aside, of course): — $ port MacPorts 2.2.99 $ sudo port install https://neverpanic.de/documents/mpstats.tar . . . $ port installed mpstats The following ports are currently installed: mpstats @0.1.3_0 (active) $ port notes mpstats Error: The port 'mpstats' was not found — but as one can see MacPorts claims - when asking for the port's notes - that the port isn’t installed!!!? It didn't say it wasn't installed; it said it wasn't found. The notes you requested would come from the normal portfile, not from any installed copy of the port. So something is the matter with the portfile? Where is the portfile? I don't see it in the port list. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On 20 Mar 2014, at 23:26 , Ryan Schmidt ryandes...@macports.org wrote: It didn't say it wasn't installed; it said it wasn't found. OK. The notes you requested would come from the normal portfile, not from any installed copy of the port. I see now. So something is the matter with the portfile? Where is the portfile? I don't see it in the port list. Since I used the tar file to install the port this caused the confusion. Thanks for clarifying this, Ryan. Greets, Marko ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On Mar 20, 2014, at 5:18 PM, mk-macpo...@techno.ms wrote: On 20 Mar 2014, at 20:19 , Clemens Lang c...@macports.org wrote: https://neverpanic.de/documents/mpstats.tar I installed the latest testing beta just OVER my stable MacPorts (keeping a copy of /opt/local put aside, of course): — $ port MacPorts 2.2.99 $ sudo port install https://neverpanic.de/documents/mpstats.tar . . . $ port installed mpstats The following ports are currently installed: mpstats @0.1.3_0 (active) $ port notes mpstats Error: The port 'mpstats' was not found — but as one can see MacPorts claims - when asking for the port's notes - that the port isn’t installed!!!? Also tab completion suddenly doesn’t work anymore… — $ port installed mpPRESSED TAB HERE mpfr mpvim — What’s going on here??? Perhaps I need to reboot? ;-) ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users Did you add your local port path back into the following file? /opt/local/etc/macports/sources.conf -- Marius Schamschula ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On Mar 20, 2014, at 17:32, mk-macpo...@techno.ms wrote: Since I used the tar file to install the port this caused the confusion. Yes, that'll be the reason. I overlooked that in your mail. I haven't used the method to install a port... ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On Thu, Mar 20, 2014 at 05:45:31PM -0500, Ryan Schmidt wrote: Since I used the tar file to install the port this caused the confusion. Yes, that'll be the reason. I overlooked that in your mail. I haven't used the method to install a port... I'm not surprised -- it's undocumented and potentially dangerous to do sudo port install $some-random-url-from-the-internet It's just as bad as ruby -e $(curl -fsSL $if-you-know-what-I-mean) However, I noticed this was possible when I ripped out some of the mport:// source sync code and was asked to put it back in, especially because it can be used to install older versions from the binaries archives we publish on packages.macports.org. If you run port notes https://neverpanic.de/documents/mpstats.tar it'll work just fine. -- Clemens Lang ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: MacPorts 2.3.0-beta1 now available for testing
On 21 Mar 2014, at 02:51 , Clemens Lang c...@macports.org wrote: port notes https://neverpanic.de/documents/mpstats.tar This is what I get from a non-sudo user here: — $ port notes https://neverpanic.de/documents/mpstats.tar Can't map the URL 'https://neverpanic.de/documents/mpstats.tar' to a port description file (Port remote fetch failed: You do not have permission to write to /opt/local/var/macports/portdirs). Please verify that the directory and portfile syntax are correct. Error: Can't open URL 'https://neverpanic.de/documents/mpstats.tar' as a port Error: Improper expression syntax while processing parameters — ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
