I am using the audio/sox port. Currently, it has ffmpeg
as a dependency (to provide libavcodec.dylib); that pulls
in all the dependencies of ffmpeg, including the whole
xorg-* world.
I think this is unnecessary for a neat audio application that SoX is,
and the ffmpeg should only be a variant. The
Below is a port of http://sourceforge.net/projects/opencore-amr/
- an implementation of the AMR voice codec.
I have tested this on 10.5.8 on a intel-based macbook.
Can people please test it further on different architetures
and macos versions?
Once it is OK, what do I need to do to get it
Below is an update to audio/sox which
- fixes checksums
- changes the description to the author's original
- fixes a hidden dependency on audio/opencore-amr
- fixes a hidden dependency on audio/lame
- fixes a hidden dependency on audio/libogg
- fixes a hidden dependency on archivers/zlib
- fixes
I have looked further into the ffmpeg functionality of SoX;
now I want to remove ffmpeg support altogether.
Compiling ffmpeg into SoX means dependency on
/opt/local/lib/libavformat.dylib
/opt/local/lib/libavcodec.dylib
/opt/local/lib/libavutil.dylib
(obviously), and the added support for
On Mar 13 17:10:28, michael sparacio wrote:
Is there a recommended port that will listen to a range of tcp ports? I am
playing with netcat but it seems it can only listen to a single port at a
time. I'd like to open hundreds or even thousands of tcp ports for firewall
screens testing.
Run
On Mar 15 22:21:12, Brandon Allbery wrote:
OpenSSL as a project desperately needs to be replaced with something sane.
Replaced where? OpenSSL and OpenSSH are both intimately related to (and
developed on) OpenBSD; there is no way they will 'replace' it with some
other implementation.
On Mar 30 03:09:32, Joshua Root wrote:
Short version: Our domain registrar, gkg.net, is threatening to cancel
the registration of macports.org and other domains that redirect to it.
We do not know whether they will follow through on this threat.
If they do, we will have no choice but to move
On Mar 29 16:17:04, Peter Schmitt wrote:
Hi macports-users!
I installed some ports on a build machine. I then build my application
and `otool -L myApp.binary` shows dependencies on some MacPorts
libraries installed at /opt/local/lib.
At this point, it doesn't matter that those libraries
On Apr 03 17:54:05, saiwingy wrote:
Since MacPorts is not compatible with /usr/local, every time I install/update
ports I had to
sudo mv /usr/local /usr/local.bak
Why would you move /usr/local?
Macports live under /opt/local by default
and have nothing to do with /usr/local.
Since MacPorts is not compatible with /usr/local, every time I
install/update
ports I had to
sudo mv /usr/local /usr/local.bak
Why would you move /usr/local?
Macports live under /opt/local by default
and have nothing to do with /usr/local.
Having things installed in
On Apr 04 10:17:23, Chris Jones wrote:
Hi,
I thought the whole reason for living under /opt/local was *not* to
interfere with /usr/local. How exactly does having /usr/local interfere?
Things from macports silently picking up things from /usr/local?
Is that the problem?
The issue is some
I just find it quite extreme to expect the user to not have
/usr/local around. The reason macports uses /opt/local (if I am
not wrong) is that macports realizes that people *do* have
/usr/local around.
I, personally, have had /usr/local around for forever. The issue is that if
you
On Apr 04 10:22:37, Jeremy Lavergne wrote:
OK, I can understand that. Did I really miss this bit
in the documentation? Can someone point me please?
I believe it should be clearly stated in the Guide.
It is not in the Guide, however the FAQ wiki page references it:
On Apr 04 10:34:48, Jeremy Lavergne wrote:
Yes, that's what I have read. But that just says why macports
uses /opt/local: because it cannot use /usr/local, for the reasons listed.
This here is something *different*: namely, that
(1) There might still be problems if the user has
obviously exists already.
`PATH=$PATH:$HOME/bin`
That puts it last in the path, which is probably
not what you intended.
On Apr 4, 2012, at 10:55, Jan Stary wrote:
In fact, I believe it is a good candidate for a FAQ immediately
following https://trac.macports.org/wiki/FAQ#defaultprefix:
Q: So
On Apr 04 16:05:27, Jeremy Lavergne wrote:
/usr/local is not a viable choice because some software
(especially auto* tools from Gnu) look in /usr/local
as a default location, which means MacPorts can't be
easily isolated when needed.
I want to kindly ask the person who wrote this to
On Apr 04 23:32:26, Dominik Reichardt wrote:
On 04.04.2012, at 23:20, Jan Stary wrote:
On Apr 04 16:05:27, Jeremy Lavergne wrote:
/usr/local is not a viable choice because some software
(especially auto* tools from Gnu) look in /usr/local
as a default location, which means MacPorts
It's the usual Unixy place for third party software, a point you yourself
made at some point; how is it you are now unaware of it?
Oh I am aware of it, and specifically mention it about
two lines below the point where you cut my message, as you know.
Nobody uses more then one port system on
No it didn't magically ended up there. You installed it there.
And you were told before you installed it there that it will
end up there.
I didn't say that, I said *magically*.
Of course I know there was no magic involved. Phew...
Jesus, I am not implying you think it was magic.
I am
The user does not know where they installs things.
Packaged installers, the users just click through.
The user is typically unaware of where packaged software is installed. You
can look at our mounds of trouble tickets that were caused by this specific
reason.
The user simply ran some
If I keep MacPorts in its own prefix, it is easier to ensure that other
software on my system does not get mixed up in a build.
No, not really. You have macports stuff in its own prefix, namely,
/opt/local. However, if a given port silently picks up something
incompatible in /usr/local, if
I agree now that /usr/local is on fact a bad choice.
What I find cnfusing or unclear is the reasoning about it
in the the FAQ.
The most prominent reason given to me yesterday for not having
/usr/local as a default prefix was that people will stupidly
rewrite the stuff in there by blindly
On Apr 05 09:00:44, Jan Stary wrote:
However, if a given port silently picks up something
incompatible in /usr/local, if might fail and often will.
Having macports isolated in /opt/local DID NOT save you from this.
Removing /usr/local is what did.
One more point to this: what
On Apr 05 10:49:01, Dominik Reichardt wrote:
As far as I can tell, /usr in PATH is being honored
opposed to /usr/local being picked up automatically.
I don't know how honored differs from being picked up,
but PATH has nothing to do with this.
Am 05.04.2012 um 10:25 schrieb Jan Stary h
On Apr 05 11:06:51, Dominik Reichardt wrote:
Honoring the order in PATH so when /opt/local is in front of /usr,
compilers will honor that.
PATH is where the binaries are looked for.
I am talking about libraries; compilers do not look
for libraries in PATH.
So yes PATH has a lot to do with
an old, incompatible version of openssl in
/usr/lib/libssl.*, and a port that fails to build
because it picks that up.
What happens then? Should I temporarily rename /usr
so that the port does not pick that up and builds successfully?
Am 05.04.2012 um 10:25 schrieb Jan Stary h...@stare.cz
On Apr 05 19:52:23, Christopher Vance wrote:
I'll also mention that OpenBSD exclusively uses packages which are
compiled elsewhere; all ported software is installed from packages;
they have already reached where NetBSD is trying to get to.
In addition, OpenBSD culture is to install from
On Apr 05 08:47:47, Arno Hautala wrote:
On 2012-04-05, Jan Stary h...@stare.cz wrote:
(The XXX is where my English fails me. Could a native speaker
put the right verb in please that seems to slip my mind?)
[...]
While this could be XXXed off as the user's own error, it is a fact
On Apr 05 08:25:49, Bradley Giesbrecht wrote:
On Apr 5, 2012, at 12:00 AM, Jan Stary wrote:
Again, this is not entirely true: the proper way for a port to
not accidently pick up unwanted dependencies is to say --disable-whatever
in the Portfile (and yes, I have run into that problem
OK, here is what I propose as a relacement/extension of FAQ#defaultprefix.
* Why is /opt/local the default install location for MacPorts?
* So with macports under /opt/local I can use /usr/local freely?
I just commited this (fixing the typos.)
https://trac.macports.org/wiki/FAQ#defaultprefix
I am willing to help this with ports that interest me.
Is there a way in trac to specifically select the ports
that have this problem?
not that I know of (since you don't know what is going to be
in /usr/local on any machine)
I tried searching in both the mailing list archives and trac;
On Apr 18 12:01:12, Murray Eisenberg wrote:
1. Without using MacPorts, I directly installed TeXLive 2011 (as
part of MacTeX).
I didn't realize that that distribution included the source files
and build/install instructions for the asymptote application. So ...
2. I used MacPorts to install
On Apr 15, 2012, at 10:56 AM, Michael_google gmail_Gersten wrote:
I am not sure which version of Wine to install from Macports (there
are three), or if this is even the right approach for what I want to
do.
The goal: Edit a movie (screen recording), from the view that 80-90%
of what
On Feb 09 20:30:50, listmeis...@thestoneforge.com wrote:
On Feb 09, 2013, at 14:24, Comer Duncan comer.dun...@gmail.com wrote:
I am wondering what the gurus say is a reasonable
update interval for macports?
This hardly takes a guru: update when you need to.
I am building libsndfile from git on MacOSX 10.5.8.
I know we have a port; I am experimenting with the source.
Building from the source needs ./autogen.sh to be run.
That's when I run into a problem:
Script started on Wed Feb 20 21:41:40 2013
hans@mac:libsndfile$ ./autogen.sh
-n checking for
On Feb 13 18:59:45, lar...@macports.org wrote:
On Feb 13, 2013, at 6:23 PM, Alejandro Imass aim...@yabarana.com wrote:
Linux tutorials (which are plentiful) will work as well, but remember that
Mac OS X is more BSD-like with some Linux accents like the bash shell.
I don't see how bash
On Feb 19 21:38:06, guanoape...@gmx.ch wrote:
Is there a black list for Tarot and other Black magic?
I took the liberty of creating one for you:
Tarot
Black Magic
My customer wishes internet filter based on Catholic Church morale.
I assume your customer is demented, or at
I am trying to install SoX using a binary package on my 10.5.8
which is
$ uname -a
Darwin mac.stare.cz 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15
16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
The attempt to install with
sudo port -v -b install sox
fails and the log says
On Feb 21 11:05:23, dl...@geeklair.net wrote:
On Feb 21, 2013, at 10:05 AM, Bruce Miller bruce.mil...@nist.gov wrote:
With MacPort's perl 5.12, the executable is installed in
/opt/local/libexec/perl5.12/sitebin
On my MacOSX 10.5.8. with macports 2.1.3 it is not, thank god:
hans@mac:~$ cd
On Feb 21 11:05:23, dl...@geeklair.net wrote:
On Feb 21, 2013, at 10:05 AM, Bruce Miller bruce.mil...@nist.gov wrote:
With MacPort's perl 5.12, the executable is installed in
/opt/local/libexec/perl5.12/sitebin
which is *NOT* where people expect to find programs.
And it's NOT a directory
On Feb 21 11:46:29, dl...@geeklair.net wrote:
On Feb 21, 2013, at 11:37 AM, Bruce Miller bruce.mil...@nist.gov wrote:
And, let's be frank; Macs cater (wisely, perhaps) to
a group of users who don't know about, or want to know about, $PATH.
... and those people tend to not ever use the
On Feb 21 18:19:56, bruce.mil...@nist.gov wrote:
As much as you or I may like to stay within managed packages,
you never can keep up with CPAN and shouldn't try.
Why can't you? Why shouldn't you try?
Whenever there is stuff in CPAN that you want to have
on your macos, make a port of it, and
On Feb 21 22:02:19, dl...@geeklair.net wrote:
On Feb 21, 2013, at 6:19 PM, Bruce R Miller bruce.mil...@nist.gov wrote:
But a plain perl used from commands like
perl Makefile.PL
will use the more common installation directories,
like macports used to do, and every other OS does.
It does
On Feb 23 12:49:48, bruce.mil...@nist.gov wrote:
On 02/23/2013 12:44 PM, Jan Stary wrote:
On Feb 21 11:05:23, dl...@geeklair.net wrote:
On Feb 21, 2013, at 10:05 AM, Bruce Miller bruce.mil...@nist.gov wrote:
With MacPort's perl 5.12, the executable is installed in
/opt/local/libexec
On Feb 23 12:43:10, pixi...@macports.org wrote:
On Feb 23, 2013, at 11:49 AM, Jan Stary wrote:
On Feb 21 11:05:23, dl...@geeklair.net wrote:
On Feb 21, 2013, at 10:05 AM, Bruce Miller bruce.mil...@nist.gov wrote:
With MacPort's perl 5.12, the executable is installed in
/opt/local
On Feb 23 17:31:17, jon...@hep.phy.cam.ac.uk wrote:
Hi,
On 23 Feb 2013, at 05:17 PM, Jan Stary h...@stare.cz wrote:
On Feb 23 16:17:26, jon...@hep.phy.cam.ac.uk wrote:
Hi,
Are binary packages for darwin9 being built?
I think not. They are only available for OSX 10.6 (darwin 10
On Feb 23 21:53:13, jon...@hep.phy.cam.ac.uk wrote:
The top section says that macports is
targeting mainly the current Mac OS X release (10.8, A.K.A. Mountain Lion)
and the immediately previous two (10.7, A.K.A. Lion and 10.6, A.K.A. Snow
Leopard).
It might be nitpicking, but
On Feb 23 18:15:16, spooky1...@gmail.com wrote:
I'm also hoping there's some audio editing software that can do things
like work on either channel of stereo, merge stereo into mono,
add/delete/edit audio chunks, combine audio samples (in series), blend them,
modify volume level (overall or
On Feb 24 06:20:53, spooky1...@gmail.com wrote:
On Sat, Feb 23, 2013 at 11:33:40PM -0600, Ryan Schmidt wrote:
Well, the binary version that I found failed---it requires Mt Lion or
better.
What exactly is your MacOSX version (uname -a)?
How exactly did you try to install the binary package?
On Feb 24 07:24:15, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 01:42:30PM +0100, Jan Stary wrote:
On Feb 24 06:20:53, spooky1...@gmail.com wrote:
On Sat, Feb 23, 2013 at 11:33:40PM -0600, Ryan Schmidt wrote:
What exactly is your MacOSX version (uname -a)?
Darwin n5ial-1.local
On Feb 24 08:05:02, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 07:24:15AM -0600, Jim Graham wrote:
Ok...what is the command to run kdenlive?
Never mind this...I read deeper into the port man page and found
the right port command to point me to kdenlive, and installed
and ran
On Feb 24 08:23:36, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 03:01:36PM +0100, Jan Stary wrote:
On Feb 24 07:24:15, spooky1...@gmail.com wrote:
This one had a pkg file, so
I just double-clicked on it. It then asked me which drive to install it
on---either my main hard
On Feb 24 10:27:09, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 04:54:21PM +0100, Jan Stary wrote:
On Feb 24 08:05:02, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 07:24:15AM -0600, Jim Graham wrote:
Ok...what is the command to run kdenlive?
Never mind this...I
On Feb 24 17:30:12, n...@syndicat.com wrote:
Am Sonntag, 24. Februar 2013, 10:27:09 schrieb Jim Graham:
From macports? What's the kdenlive APP,
as opposed to macport's multimedia/kdenlive?
Mainly for audio ardour2 (and the upcoming 3) is worth a look as it aims to
provide a full
On Feb 24 10:48:24, spooky1...@gmail.com wrote:
ardour2 is in macports. The site for the binary version demands money
for the Mac OS X working version (or you get a demo that doesn't save
anything). Considering that I currently have $1.38 to last until my
next disability payment in March,
On Feb 24 12:29:11, allber...@gmail.com wrote:
On Sun, Feb 24, 2013 at 12:21 PM, Jim Graham spooky1...@gmail.com wrote:
always been flaky (and useless even when it runs, as you need to install
all the KDE dependencies with debug symbols for it to be able to do
anything at all useful).
On Feb 24 15:35:58, spooky1...@gmail.com wrote:
So does just double clipping the app in Finder work? It does for me...
And now the real reason for this response. I haven't put the icon in
finder's Applications folder (which I rarely use anyways), but it is in
the dock, and yes, it works
On Feb 24 12:07:14, allber...@gmail.com wrote:
On Sun, Feb 24, 2013 at 10:54 AM, Jan Stary h...@stare.cz wrote:
the right port command to point me to kdenlive, and installed
and ran kdenlive.app.
From macports? What's the kdenlive APP,
as opposed to macport's multimedia/kdenlive
On Feb 24 14:51:07, sewebs...@gmail.com wrote:
On Sun, Feb 24, 2013 at 2:50 PM, Jan Stary h...@stare.cz wrote:
Does that mean that macports installs stuff out of /opt/local?
For example, under /Applications?
Yes.
Do we mention it in the Guide or in the FAQ?
There was this whole debate
On Feb 24 17:03:57, spooky1...@gmail.com wrote:
On Sun, Feb 24, 2013 at 11:48:38PM +0100, Jan Stary wrote:
On Feb 24 15:35:58, spooky1...@gmail.com wrote:
And now the real reason for this response. I haven't put the icon in
finder's Applications folder (which I rarely use anyways
On Feb 24 17:48:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 12:41:17AM +0100, Jan Stary wrote:
That's not how macport's ports are installed. You don't have to move
any icon anywhere.
No, of course you don't. But as you already know, having read my post
before commenting
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham spooky1...@gmail.com wrote:
There is nothing wrong with KDE, as long as you properly install the
On Feb 25 00:05:09, jer...@lavergne.gotdns.org wrote:
Crown was a lovely autocorrect for cron
Crown job sounds a bit nasty though.
___
macports-users mailing list
macports-users@lists.macosforge.org
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3) Deliver the messages in another manner: eg, cause them to open
in TextEdit or a browser window.
That needs the capability
On Feb 25 11:18:38, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 07:56:13AM -0800, Bradley Giesbrecht wrote:
On Feb 25, 2013, at 5:42 AM, Jim Graham wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
3
On Feb 25 08:57:09, ctrelea...@cogeco.ca wrote:
At 2:05 PM +0100 2/25/13, Jan Stary wrote:
On Feb 24 20:50:52, ctrelea...@cogeco.ca wrote:
At 5:23 PM -0600 2/24/13, Jim Graham wrote:
On Sun, Feb 24, 2013 at 11:03:54PM +, Chris Jones wrote:
On 24 Feb 2013, at 10:59pm, Jim Graham
On Feb 25 16:12:12, spooky1...@gmail.com wrote:
Back way before I expected to be able to return. Strange.
On Mon, Feb 25, 2013 at 08:13:39PM +0100, Jan Stary wrote:
On Feb 25 07:42:04, spooky1...@gmail.com wrote:
On Mon, Feb 25, 2013 at 02:05:07PM +0100, Jan Stary wrote:
On Feb 24 20
On Feb 26 10:12:57, pixi...@macports.org wrote:
On Feb 25, 2013, at 3:42 PM, Jan Stary wrote:
The modification IMHO belongs to port(1) itself:
remember what was installed in this run, then
print out all the messages (as opposed to printing
every message just after the given port
If you reply to a message to this list on this list
(as opposed to off-list), please reply To: the list.
Increasingly often, I see people replying To: the original
poster, with Cc: to the list. Such a message does reach
the recipients, but
(1) it breaks the list functionality:
none of the
On Feb 26 15:44:12, jer...@lavergne.gotdns.org wrote:
There is nothing wrong with that;
apparently I need to re-read the port manpage.
However, this still requires an action of the user besides 'install';
I believe that the notes of the newly installed packages (if any)
should be
On Feb 26 16:34:07, jer...@lavergne.gotdns.org wrote:
The suggested 'port notes' works for a given package;
for example, if I run 'port install package', I can run
'port note depof:package' after that and get all the notes,
in one place. But:
(1) this should happen automatically
On Feb 26 15:27:57, spooky1...@gmail.com wrote:
On Tue, Feb 26, 2013 at 09:41:18PM +0100, Jan Stary wrote:
Increasingly often, I see people replying To: the original
poster, with Cc: to the list. Such a message does reach
the recipients, but
(1) it breaks the list functionality
On Feb 26 16:56:23, jer...@lavergne.gotdns.org wrote:
Surely the install process does some maintenance at its exit
(read: catches signals), and can spit out those messages even
if it is exiting due to being interrupted (as opposed to
finishing without error).
If MacPorts is quitting
On Feb 26 23:22:46, h...@stare.cz wrote:
On Feb 26 16:56:23, jer...@lavergne.gotdns.org wrote:
Surely the install process does some maintenance at its exit
(read: catches signals), and can spit out those messages even
if it is exiting due to being interrupted (as opposed to
finishing
On Feb 26 17:35:45, jer...@lavergne.gotdns.org wrote:
And even if he wanted to kill the ongoing installation,
why would he close the window, as opposed to simply
killing the process in that (terminal) window?
There's a button there, the user can hit it.
To lose any possibility of
On Feb 26 15:37:45, sewebs...@gmail.com wrote:
On Tue, Feb 26, 2013 at 3:04 PM, Jan Stary h...@stare.cz wrote:
I agree, in such situations we cannot do anything.
How does that make install messages interspersed
in various places in the install output better
than having them at one place
On Feb 26 22:01:36, ctrelea...@cogeco.ca wrote:
At 11:56 PM +0100 2/26/13, Chris Jones wrote:
A simple notes happened above message would be ideal.
Conversely, we'd be spewing twice as many messages
if the install isn't interrupted.
Why? If the messages were _only_ printed at the
While looking at various package's notes
(during the ongoing install notes debate),
I noticed a port with the following notes:
virtuoso has the following notes:
Disable antivirus when building this port.
Arguably, it is not of much use to the user
displaying this note _after_ the
On Mar 25 00:33:21, scottclau...@mac.com wrote:
Hello,
After a recent update of Macports I now have the following constantly running
in Mountain Lion terminal:
# MacPorts Installer addition on 2009-11-22_at_17:22:04: adding an
appropriate PATH variable for use with MacPorts.
export
On May 26 11:19:24, pengyu...@gmail.com wrote:
Hi,
Besides manually link gmake to make (also manpage), is there a way in
macports to like gmake to make?
Why would you want to do that?
Also man gmake shows the following.
Should it be updated?
COPYRIGHT
Copyright (C) 1992, 1993,
On May 28 21:36:58, jon...@hep.phy.cam.ac.uk wrote:
Hi,
On 28 May 2013, at 08:12 PM, Jean-François Caron jfca...@phas.ubc.ca wrote:
While download statistics might not be a good system, I do concur that
MacPorts very much would benefit from having a discovery mechanism by
which users
On Jun 11 07:53:22, pixi...@macports.org wrote:
On Jun 11, 2013, at 6:46 AM, Jan Stary wrote:
On May 28 21:36:58, jon...@hep.phy.cam.ac.uk wrote:
Hi,
On 28 May 2013, at 08:12 PM, Jean-François Caron jfca...@phas.ubc.ca
wrote:
While download statistics might not be a good
On Jul 04 09:44:06, rai...@krugs.de wrote:
Hi
I am using homebrew at the moment, but there are certain packges, which
are not on homebrew (e.g. awesome and kde apps).
Create a homebrew port of awesome.
That way, not only will you get what you wanted,
but everyone will benefit from the
I am trying to build sysutils/tmux on MacOSX 10.4.11
It fails because 10.4.11 (Darwin 8.11.0) does not have
libproc.h that is included by tmux's osdep-darwin.c:
osdep-darwin.c:22:21: error: libproc.h: No such file or directory
This problem has been encountered before,
and there is even a known
On Oct 27 17:12:56, bun...@gmail.com wrote:
sudo port content dvdrip shows:
/opt/local/libexec/perl5.12/sitebin/dvdrip
/opt/local/libexec/perl5.12/sitebin/dvdrip-exec
/opt/local/libexec/perl5.12/sitebin/dvdrip-master
/opt/local/libexec/perl5.12/sitebin/dvdrip-multitee
On Oct 28 00:21:19, macpo...@metaspasm.org wrote:
On Mon, 28 Oct 2013, Brandon Allbery wrote:
On Sun, Oct 27, 2013 at 5:12 PM, bunk3m bun...@gmail.com wrote:
/opt/local/libexec/perl5.12/sitebin/dvdrip
/opt/local/libexec/perl5.12/sitebin/dvdrip-exec
#42846: libsndfile @1.0.25 fails linking phase on mavericks 10.9.2
-+
Reporter: mtb19@??? | Owner: hans@???
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports |Version:
On Apr 10 18:48:01, vit...@yandex.ru wrote:
Yes, but MacPorts can control this.
Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH
in ~/.bash_profile it can (and should) specify it system-wide
in /etc/bashrc
Absolutely not. Don't any program dare touch things in /etc.
On Apr 11 07:55:47, h...@stare.cz wrote:
On Apr 10 18:48:01, vit...@yandex.ru wrote:
Yes, but MacPorts can control this.
Instead of specifying export PATH=/opt/local/bin:/opt/local/sbin:$PATH
in ~/.bash_profile it can (and should) specify it system-wide
in /etc/bashrc
Absolutely not.
On Apr 08 09:00:24, rjvber...@gmail.com wrote:
These days I spend my time switching back and forth between Linux/Debian and
OS X. The various package management tools I use on the former (apt, apt-get,
aptitude) all have a very similar syntax, but port has a number of
just-or-completely
At this point, one could tell that you conme from linux
even if you hadn't said so .
So? What's the point? What if I had suggested reading the table from a plist?
I don't remember the names of these commands.
Please change your utility so that it lets me
specify a table that replaces these
On May 03 12:27:18, billc_li...@greenbuilder.com wrote:
I installed a non-MacPorts package on my server the other day -
WordPress command line interface (wp-cli) which uses the wp
command. It's working properly.
But I just went to do my regular updates using MacPorts, and I've
lost my port
I am getting the following error while trying to compile a LaTeX file:
! LaTeX Error: File `everyshi.sty' not found.
I have the following texlive-* package installed:
texlive-basic @34245_0+doc
texlive-bin@2014_1+x11
texlive-common
http://trac.macports.org/wiki/TeXLivePackages
The above indicates ms is part of texlive-latex-recommended.
Thanks, the above link is what i was missing.
Jan
___
macports-users mailing list
macports-users@lists.macosforge.org
On Sep 05 16:48:44, allber...@gmail.com wrote:
On Fri, Sep 5, 2014 at 4:43 PM, Alejandro Imass aim...@yabarana.com wrote:
On Fri, Sep 5, 2014 at 4:36 PM, Dave Horsfall d...@horsfall.org wrote:
On Fri, 5 Sep 2014, Alejandro Imass wrote:
Yeah MacPorts is the most awesome piece of
On Sep 23 10:57:22, allber...@gmail.com wrote:
On Tue, Sep 23, 2014 at 10:55 AM, Jan Stary h...@stare.cz wrote:
Have a look at OpenBSD's pkg_add(1)
pkg is great if you can get away with defaults for everything. I always
find myself forced into ports
Putting back the context that you
On Sep 27 09:53:02, allber...@gmail.com wrote:
On Sat, Sep 27, 2014 at 6:59 AM, Jan Stary h...@stare.cz wrote:
Generaly, I find the precompiled defaults quite sensible
in most of the packaging systems, having subpackages/flavors/variants etc.
it surprises me that you always need
You will be using the mirror until you revert your changes. I would restore
the default configuration so you don't get caught mistakenly thinking that
'rsync.macports.org' is down when it's your mirror that went down!
On the contrary, you should be using
a mirror close to you for regular
This is MacOSX 10.5.8/i386 using MacPorts 2.3.3
Darwin mac.stare.cz 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15
16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386
I am trying to install databases/libpqxx.
The build fails with main.log saying (full log below):
:info:build make[3]:
On Mar 05 14:26:37, c...@macports.org wrote:
I don't know why it exists, but a couple of top-level directories
are symlinked into /private.
In my case,
$ ls -l /private/
total 0
drwxr-xr-x 103 root wheel 3502 Mar 2 21:21 etc/
drwxr-xr-x2 root wheel68 Sep 24 2007 tftpboot/
1 - 100 of 115 matches
Mail list logo
