Well, I choose to compile my variants first, like +ipv6, so that any
dependancies don't get hosed. As in, if you need to install curl +ipv6
but, another port needs curl then if you don't compile the variant
first, then you will compile the non-ipv6 version to satisfy the
dependancy and then have
On Jun 18, 2009, at 10:32, Darren Weber wrote:
I have attended WWDC2009, where I got access to a developer version
of Snow
Leopard (and SL server) and the latest Xcode tools bundled with the
SDK for
iPhone 3.0.
If I can learn how to create a dual-boot system (so I can hang onto
everything
Scott C. Kennedy wrote:
You will lose your variants, if you made any custom builds. I keep a
shell script with the variants and ports that I use up to date, plus I
keep and compare the port installed output from before and after to
ensure I didn't miss anything.
How is that script
On Jun 15, 2009, at 17:05, Darren Weber wrote:
MacPorts doesn't include a command to help you rebuild an entire
installation like this. This is unfortunate and makes it a rather
involved process. But since upgrading to a new major OS version is
a task users don't perform often, I don't
On Tue, Jun 9, 2009 at 5:32 PM, Ryan Schmidt ryandes...@macports.orgwrote:
On Jun 9, 2009, at 17:07, Jeremy Huddleston wrote:
On Jun 9, 2009, at 13:36, Darren Weber wrote:
What's the recommended series of command lines for that?
Here's what I did:
cd /opt/local/var/macports/software
On Tue, Jun 9, 2009 at 5:45 AM, vincent habchi vi...@macports.org wrote:
Le 9 juin 09 à 14:32, Kurt Hillig a écrit :
On the other hand I recently upgraded from 10.4 to 10.5 and my machine was
horribly unstable until I blew away the MacPorts install. I'm not sure why
this was, and I didn't
Hi Darren,
On Tue, Jun 9, 2009 at 1:20 AM, Darren Weberdwe...@macports.org wrote:
What happens to a MacPorts installation when we install a distribution
upgrade to OSX, say Leopard to Snow Leopard? Do we need to backup the
MacPorts installation, or is the ${prefix} path immune to the upgrade?
Le 9 juin 09 à 14:32, Kurt Hillig a écrit :
On the other hand I recently upgraded from 10.4 to 10.5 and my
machine was horribly unstable until I blew away the MacPorts
install. I'm not sure why this was, and I didn't have the time or
gumption to run a lot of diagnostics, so it could well
On 2009-6-9 22:15, Tim Visher wrote:
Hi Darren,
On Tue, Jun 9, 2009 at 1:20 AM, Darren Weberdwe...@macports.org wrote:
What happens to a MacPorts installation when we install a distribution
upgrade to OSX, say Leopard to Snow Leopard? Do we need to backup the
MacPorts installation, or is
What's the recommended series of command lines for that?
Thanks!
Darren
On Tue, Jun 9, 2009 at 8:19 AM, Joshua Root j...@macports.org wrote:
On 2009-6-9 22:15, Tim Visher wrote:
Hi Darren,
On Tue, Jun 9, 2009 at 1:20 AM, Darren Weberdwe...@macports.org wrote:
What happens to a MacPorts
Here's what I did:
cd /opt/local/var/macports/software
/bin/ls -1d * ~/todo.mp
cd
sudo mv /opt/local /var/tmp/old_macports
cd src/macports/trunk/base
./configure make sudo make install
for f in $(cat todo.mp ); do [[ -d /opt/local/var/macports/software/
$f ]] || sudo port -v install $f; done
You will lose your variants, if you made any custom builds. I keep a
shell script with the variants and ports that I use up to date, plus I
keep and compare the port installed output from before and after to
ensure I didn't miss anything.
Scott
Jeremy Huddleston wrote:
Here's what I did:
cd
On Jun 9, 2009, at 17:07, Jeremy Huddleston wrote:
On Jun 9, 2009, at 13:36, Darren Weber wrote:
What's the recommended series of command lines for that?
Here's what I did:
cd /opt/local/var/macports/software
/bin/ls -1d * ~/todo.mp
cd
sudo mv /opt/local /var/tmp/old_macports
Moving
What happens to a MacPorts installation when we install a distribution
upgrade to OSX, say Leopard to Snow Leopard? Do we need to backup the
MacPorts installation, or is the ${prefix} path immune to the upgrade? What
about startup items (launchd or anything that violates the mtree)?
Thanks in
14 matches
Mail list logo
