On Mon, Apr 02, 2012 at 09:22:29PM -0500, Jeremy Lavergne wrote:
Don't invoke xcodebuild, but instead xcodebuild -license:
https://trac.macports.org/wiki/ProblemHotlist#xcode-eula
I hope that error message has been updated but simply not released to the
users yet. Sorry about the misleading
On Apr 3, 2012, at 01:19, Dan Ports wrote:
I hope that error message has been updated but simply not released to the
users yet. Sorry about the misleading text.
That error message actually comes from xcodebuild directly, not from
us.
In that case, I hope that error message has been
I know (and am grateful!) that FFmpeg is available via MacPorts.
However, FFmbc[1] is allegedly[2] better than FFmpeg for rewrapping AVCHD
files.
I wonder if FFmbc might be added to MacPorts?
Many thanks,
Sam
[1] http://code.google.com/p/ffmbc/
[2]
On 3 April 2012 07:52, Sam Kuper sam.ku...@uclmail.net wrote:
I know (and am grateful!) that FFmpeg is available via MacPorts.
However, FFmbc[1] is allegedly[2] better than FFmpeg for rewrapping AVCHD
files.
I wonder if FFmbc might be added to MacPorts?
Ah, I was behind the curve:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/04/2012 03:36, Puneet Kishor wrote:
I just reinstalled postgresql91-server, and am revisiting a
question I asked a few months ago. I am looking for the correct way
for configuring and launching postgresql automatically when
computer starts.
On Apr 3, 2012, at 12:42 AM, Dan Ports wrote:
The spi contrib module seems like it'd be a weird choice for a port,
though, since I thought its value was mostly as an example for how to
use the SPI API, not something you'd use directly.
I am interested in the timetravel capability of SPI as
Hello:
How do I rebuild all installed ports dependent on a specific port? Overall, I'd
like MacPorts to update the outdated ports and then rebuild the ports that used
the outdated ports so everything was compiled with the latest versions of
everything. I apologize if this is documented; I did
On Apr 3, 2012, at 9:23 AM, Anthony Michael Agelastos wrote:
Hello:
How do I rebuild all installed ports dependent on a specific port? Overall,
I'd like MacPorts to update the outdated ports and then rebuild the ports
that used the outdated ports so everything was compiled with the
On 2012-04-02 , at 10:45 , Ryan Schmidt wrote:
Good question. I don't know if we've ever thought about whether launchd
plists should be managed by port select. I don't have a particular opinion
about whether it would be useful or not, but if you think it is, maybe others
do too.
One
On Apr 3, 2012, at 14:44, Sam Kuper wrote:
Is Shenidam a viable candidate for being ported into MacPorts?
I'll see if I can make a port.
___
macports-users mailing list
macports-users@lists.macosforge.org
On Apr 3, 2012, at 09:24, Richard L. Hamilton wrote:
On Apr 3, 2012, at 9:23 AM, Anthony Michael Agelastos wrote:
Hello:
How do I rebuild all installed ports dependent on a specific port? Overall,
I'd like MacPorts to update the outdated ports and then rebuild the ports
that used
On 2012-04-02 , at 09:41 , Bradley Giesbrecht wrote:
This appears to work.
/opt/local/etc/mysql55/my.cnf
...
[mysqld]
plugin-load = federated=ha_federated.so
federated
Yes, that works. This works as well
from a properly privileged database user
mysql -e INSTALL PLUGIN federated
On Apr 3, 2012, at 12:59 PM, Chris Janton wrote:
On 2012-04-02 , at 10:45 , Ryan Schmidt wrote:
Good question. I don't know if we've ever thought about whether launchd
plists should be managed by port select. I don't have a particular opinion
about whether it would be useful or not, but
Since MacPorts is not compatible with /usr/local, every time I install/update
ports I had to
sudo mv /usr/local /usr/local.bak
and then after I am done building macports stuff I would move it back. This
works fine but is kind of cumbersome and sometimes the moved /usr/local
directory triggers
Since MacPorts is not compatible with /usr/local, every time I install/update
ports I had to
sudo mv /usr/local /usr/local.bak
and then after I am done building macports stuff I would move it back. This
works fine but is kind of cumbersome and sometimes the moved /usr/local
directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/2012 01:54, 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
and then after I am done building macports stuff I would move it back. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/04/2012 01:57, Jeremy Lavergne 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
and then after I am done building macports stuff I would move it back.
On Apr 3, 2012, at 19:54, 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
and then after I am done building macports stuff I would move it back. This
works fine but is kind of cumbersome and
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.
19 matches
Mail list logo
