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
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
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
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
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
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
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
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
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
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
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.
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
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
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.
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
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
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
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
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:
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
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
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
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
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
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:
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).
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:
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:
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
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):
—
$
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
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):
—
$
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...
___
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
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
35 matches
Mail list logo
