Hi,
- On 5 Feb, 2015, at 16:10, MacPorts nore...@macports.org wrote:
Page Migration was changed by heeg...@yahoo.com
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=83
Revision 83
Comment: Fixed setrequested command
Changes:
On Feb 5, 2015, at 10:04 AM, Clemens Lang c...@macports.org wrote:
Hi,
- On 5 Feb, 2015, at 16:10, MacPorts nore...@macports.org wrote:
Page Migration was changed by heeg...@yahoo.com
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=83
Revision 83
Comment:
On 15/12/14 09:38, René J.V. Bertin wrote:
For comparison: while theoretically possible, it's generally not
advised to update an Ubuntu or Debian release by simply changing the
repository definitions and letting apt figure things out. R.
Actually, Ubuntu provide do-release-upgrade (and a GUI
Yes, there were a couple of problems :-/ The version below has worked two times
in a row on Yosemite. I hope you will at least put this script or something
like it on the wiki as an alternative. It could save many people a lot of time.
#!/bin/bash
# If there is an argument, then don't preserve
@lists.macosforge.org
Subject: Re: [MacPorts] Migration modified
Date: December 15, 2014 at 4:38:17 AM EST
On Sunday December 14 2014 20:43:43 Dave Yost wrote:
Really, code to do a migration should be part of macports, IMO. Nothing
like being able to start a command and walk away for a couple of hours
On Dec 15, 2014, at 2:17 PM, Dave Yost wrote:
The message below reminds me of a feature I think would be useful and might
help with the problem he mentions: MacPorts could output a minimal list of
ports which when installed would result in the same set of ports as currently
installed, in
Putting this script in contrib and linking to it would be fine.
- Josh
On 2014-12-16 01:38 , Dave Yost wrote:
Yes, there were a couple of problems :-/ The version below has worked
two times in a row on Yosemite. I hope you will at least put this script
or something like it on the wiki as an
The migration steps weren't really intended to be run as a single script. I'm
not comfortable telling users to run this big untested blob of code.
On Dec 14, 2014, at 10:37 PM, MacPorts nore...@macports.org wrote:
Page Migration was changed by d...@yost.com
Diff URL:
On 2014-12-14, at 07:59 PM, Lawrence Velázquez lar...@macports.org wrote:
The migration steps weren't really intended to be run as a single script. I'm
not comfortable telling users to run this big untested blob of code.
Then let’s test it! Works for me on Yosemite. I’ll run it again.
You
On Oct 19, 2014, at 1:48 PM, MacPorts wrote:
Page Migration was changed by mag...@icloud.com
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=70
Revision 70
Comment: added emphasis on reinstalling Mac Ports package
Changes:
On Sun, Oct 19, 2014 at 4:49 PM, Ryan Schmidt ryandes...@macports.org
wrote:
Why add IMPORTANT - Do Not Skip this step to this step? Singling out
this step gives the erroneous impression that other steps are not important
and can be skipped. All steps are important.
Because at least two
What is the purpose of this example? Is it meant to make the
instructions simpler? If users start to read only those they will miss
lots of details of the migration process.
On 2013-10-31 04:41, MacPorts wrote:
+=== A simple example ===
+run as root
This instruction alone is not simple.
I
On 2013-10-31 01:40, Clemens Lang wrote:
=== Reinstall ports === #ports
To reinstall your ports:
1. Save the list of installed ports:
{{{
-port -qv installed myports.txt
+port -qv installed my_installed_ports.txt
+port list requested | perl -pe 's/ .*//g' | sort -u
The real correction would be addressing the litany of problems raised, or
removing all of your revisions.
On Oct 31, 2013, at 9:51, MacPorts nore...@macports.org wrote:
Comment: some corrections from rai...@macports.org
___
macports-dev mailing list
On 2013-10-31 15:12, Jeremy Lavergne wrote:
The real correction would be addressing the litany of problems raised, or
removing all of your revisions.
The intention is to give easier instructions. But the detailed
explanations are required to catch all corner cases and to give hints
what the
The example breaks down when you have a package that cannot be installed on the
new OS, such as llvm-3.0 on mavericks. You would have to uninstall all the
“bad” packages prior to running upgrade, and then do an upgrade
—enforce-variants to ensure it doesn’t get included again.
On Oct 31, 2013,
On 2013-10-31 16:06, Jeremy Lavergne wrote:
The example breaks down when you have a package that cannot be
installed on the new OS, such as llvm-3.0 on mavericks. You would
have to uninstall all the “bad” packages prior to running upgrade,
and then do an upgrade —enforce-variants to ensure it
Hi,
On Thu, Oct 31, 2013 at 12:17:00AM +, MacPorts wrote:
Page Migration was changed by elatl...@gmail.com
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=62
Revision 62
Are you sure those changes are entirely correct?
On Oct 23, 2013, at 04:37, MacPorts nore...@macports.org wrote:
Page Migration was changed by rai...@macports.org
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=58
Revision 58
Comment: Be more verbose on what to do for each OS X release
Changes:
+ 1. Edit macports.conf
+{{{
+`sudo nano ${prefix}/etc/macports/macports.conf`
+}}}
+and change
{{{
developer_dir /Developer
}}}
-to
+to
{{{
developer_dir
}}}
This is only necessary if the user has edited their macports.conf
previously, the default is for this line to be
On 17.02.2012 09:54, Eric Cronin wrote:
+ 1. Edit macports.conf
+{{{
+`sudo nano ${prefix}/etc/macports/macports.conf`
+}}}
+and change
{{{
developer_dir /Developer
}}}
-to
+to
{{{
developer_dir
}}}
This is only necessary if the user has edited their macports.conf
Never mind, this is setting it to the empty string which does actually change
something. So the before just needs to be changed to show it was commented
out by default
Thanks, updated.
___
macports-dev mailing list
On 2012-2-18 01:54 , Eric Cronin wrote:
+ 1. Edit macports.conf
+{{{
+`sudo nano ${prefix}/etc/macports/macports.conf`
+}}}
+and change
{{{
developer_dir /Developer
}}}
-to
+to
{{{
developer_dir
}}}
This is only necessary if the user has edited their
Note that the above is a hack. Setting developer_dir to the empty string
instead of /Developer means that ${developer_dir}/usr/bin/foo becomes
/usr/bin/foo, which works until you actually need something that is in
$developer_dir and not /.
By all means, edit the wiki to be more correct :-)
On 2011-3-18 16:42 , Ryan Schmidt wrote:
On Mar 17, 2011, at 23:11, Jeremy Lavergne wrote:
-port echo requested myports.txt
+port installed requested myports.txt
Ah, nice.
I figured the script Joshua wrote, at the bottom of that page, was probably
designed for the output of port
On 2011-3-18 16:47 , Ryan Schmidt wrote:
On Mar 18, 2011, at 00:42, Ryan Schmidt wrote:
Also, do we have an output with negative variants? since registry handles
this now the outputs should probably include it.
I'm not aware if we have something that does that.
Wait, yes I am. port -v
On 2011-3-18 17:23 , Joshua Root wrote:
On 2011-3-18 16:42 , Ryan Schmidt wrote:
On Mar 17, 2011, at 23:11, Jeremy Lavergne wrote:
-port echo requested myports.txt
+port installed requested myports.txt
Ah, nice.
I figured the script Joshua wrote, at the bottom of that page, was
On Mar 17, 2011, at 23:11, Jeremy Lavergne wrote:
-port echo requested myports.txt
+port installed requested myports.txt
Ah, nice.
I figured the script Joshua wrote, at the bottom of that page, was probably
designed for the output of port installed not the output of port echo.
How
On Mar 18, 2011, at 00:42, Ryan Schmidt wrote:
Also, do we have an output with negative variants? since registry handles
this now the outputs should probably include it.
I'm not aware if we have something that does that.
Wait, yes I am. port -v installed would show it.
port -v installed
On Oct 15, 2010, at 09:09, MacPorts wrote:
Changed page Migration by lagrave+bugs+macosforge@gmail.com from
81.216.194.52*
Page URL: https://trac.macports.org/wiki/Migration
Diff URL: https://trac.macports.org/wiki/Migration?action=diffversion=36
Revision 36
On Jul 10, 2010, at 01:22, MacPorts wrote:
Changed page Migration by michaelrw...@att.net from 74.61.37.207*
Page URL: http://trac.macports.org/wiki/Migration
Diff URL: http://trac.macports.org/wiki/Migration?action=diffversion=35
Revision 35
Comment: Added hint for other Tcl library
On Apr 20, 2010, at 18:51, Joshua Root wrote:
On 2010-4-21 07:46 , Ryan Schmidt wrote:
On Apr 20, 2010, at 16:24, MacPorts wrote:
+This is another possibility, which will list all the ports on one {{{sudo
port install}}} command, rather than a separate command for each port. In
a
On Apr 20, 2010, at 16:24, MacPorts wrote:
+This is another possibility, which will list all the ports on one {{{sudo
port install}}} command, rather than a separate command for each port. In a
perfect world (ha! ha! ha!), this port command might resolve the dependency
tree and arrange
On 2010-4-21 07:46 , Ryan Schmidt wrote:
On Apr 20, 2010, at 16:24, MacPorts wrote:
+This is another possibility, which will list all the ports on one {{{sudo
port install}}} command, rather than a separate command for each port. In a
perfect world (ha! ha! ha!), this port command might
On 2010-1-29 23:24 , MacPorts wrote:
Changed page Migration by stig at stigbakken.com from 193.91.206.170*
Page URL: http://trac.macports.org/wiki/Migration
Diff URL: http://trac.macports.org/wiki/Migration?action=diffversion=19
Revision 19
On Jan 29, 2010, at 08:07, Joshua Root wrote:
On 2010-1-29 23:24 , MacPorts wrote:
Changed page Migration by stig at stigbakken.com from 193.91.206.170*
Page URL: http://trac.macports.org/wiki/Migration
Diff URL: http://trac.macports.org/wiki/Migration?action=diffversion=19
Revision 19
On 2010-1-30 01:19 , Ryan Schmidt wrote:
On Jan 29, 2010, at 08:07, Joshua Root wrote:
Doesn't this have the same problems as the previously featured automatic
method, `sudo port upgrade --force installed`?
I believe it does, and the same problems as the previous automatic upgrade
On 2010-1-22 12:42 , Joshua Root wrote:
On 2010-1-22 08:06 , Dan Ports wrote:
On Thu, Jan 21, 2010 at 02:45:08PM -0600, Ryan Schmidt wrote:
I don't think we want this shell script. Certainly its position in the wiki
makes it look official, and I can't endorse it. It doesn't, for example,
On Jan 21, 2010, at 14:01, MacPorts wrote:
Changed page Migration by lemontea_c...@mac.com from 17.208.104.133*
Page URL: http://trac.macports.org/wiki/Migration
Diff URL: http://trac.macports.org/wiki/Migration?action=diffversion=19
Revision 19
On Thu, Jan 21, 2010 at 02:45:08PM -0600, Ryan Schmidt wrote:
I don't think we want this shell script. Certainly its position in the wiki
makes it look official, and I can't endorse it. It doesn't, for example, take
into account three important aspects of the Migration process:
I'll take
On 01/21/2010 01:06 PM, Dan Ports wrote:
On Thu, Jan 21, 2010 at 02:45:08PM -0600, Ryan Schmidt wrote:
I don't think we want this shell script. Certainly its position in the wiki
makes it look official, and I can't endorse it. It doesn't, for example, take
into account three important aspects
On Jan 21, 2010, at 15:06, Dan Ports wrote:
I'll take your word on this particular shell script (I haven't looked
at it) -- but I think that such a script, if done right, would be a
great thing to have.
No doubt. But I claim there isn't a way to do such a script properly. Well,
maybe there
On the simple side, what about an install log. Plain text file that
simply lists the commands you issued when installing software.
Sort of like a grep 'port install' .bash_history that lasted a little
longer.
This would omit all dependencies and leave you a chronological list of
what you
On Thu, Jan 21, 2010 at 03:30:29PM -0600, Ryan Schmidt wrote:
No doubt. But I claim there isn't a way to do such a script properly. Well,
maybe there is, with proper hooks into the MacPorts dependency architecture,
but this 20-line shell script doesn't do that.
It wouldn't necessarily be a
On Jan 21, 2010, at 15:08, Blair Zajac wrote:
I would also suggest just dropping all the variants into the
$prefix/etc/macports/variants.conf instead of doing to the work in keeping
each variant around.
A curious idea. I tend to keep my variants.conf extremely sparse, containing
only
On Jan 21, 2010, at 1:06 PM, Dan Ports wrote:
I'll take your word on this particular shell script (I haven't looked
at it) -- but I think that such a script, if done right, would be a
great thing to have.
I agree. I just looked at it, comments below the script, for what they are
worth.
On 2010-1-22 08:06 , Dan Ports wrote:
On Thu, Jan 21, 2010 at 02:45:08PM -0600, Ryan Schmidt wrote:
I don't think we want this shell script. Certainly its position in the wiki
makes it look official, and I can't endorse it. It doesn't, for example,
take into account three important aspects
+ 2. Clean any partially completed builds, and uninstall all
installed ports:
{{{
+sudo port clean installed
It be much faster and thorough to use `sudo rm -rf ${prefix}/var/
macports/build/*`
Even `sudo port clean all` would be better.
___
48 matches
Mail list logo
