Horst Simon
Mobile: +61 414 303-433
Phone: +61 3 8555-2322
Email: horst.si...@optusnet.com.au mailto:hsi...@optusnet.com.au
__
Please consider your environmental
responsibility before printing this email.
This message
At 3:50 PM -0700 10/20/14, James Berry wrote:
On Oct 20, 2014, at 3:27 AM, Clemens Lang c...@macports.org wrote:
- On 20 Oct, 2014, at 08:18, Lawrence
Velázquez lar...@macports.org wrote:
On Oct 20, 2014, at 1:22 AM, Leo Singer aron...@macports.org wrote:
I found that the
Perhaps we can better judge the time spent scanning binaries if we had a final
count indicating how many were scanned.
I suspect that sometimes, such as when a build fails, all the successfully
installed dependents have not been scanned. Only once a successful build occurs
do all new binaries
On Wednesday October 22 2014 11:01:14 Jeremy Lavergne wrote:
Perhaps we can better judge the time spent scanning binaries if we had a
final count indicating how many were scanned.
I suspect that sometimes, such as when a build fails, all the successfully
installed dependents have not been
On Wed, Oct 22, 2014 at 3:34 PM, René J.V. rjvber...@gmail.com wrote:
Also, I think it's a bit (much) overkill to scan all binaries when installing
a new or upgrading an existing port. In principle MacPorts knows which ports
depend on which other ports, and it knows what files a port
On Oct 22, 2014, at 3:47 PM, Arno Hautala wrote:
I'm pretty sure that the scan only checks newly installed files.
Correct.
Only new (yet-to-be-scanned) files get added, then only the applicable files
are checked during rev-upgrade.
___
On Wednesday October 22 2014 15:51:38 Jeremy Lavergne wrote:
On Oct 22, 2014, at 3:47 PM, Arno Hautala wrote:
I'm pretty sure that the scan only checks newly installed files.
Correct.
Only new (yet-to-be-scanned) files get added, then only the applicable
files are checked during
On Oct 22, 2014, at 4:06 PM, René J.V. Bertin wrote:
What's the point in scanning newly installed files? I thought the whole idea
was to scan already installed files for ABI issues due to the newly installed
(dylib) files?
Or are we talking about the (other?) scan that bugs you after you
On Oct 22, 2014, at 1:06 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Wednesday October 22 2014 15:51:38 Jeremy Lavergne wrote:
On Oct 22, 2014, at 3:47 PM, Arno Hautala wrote:
I'm pretty sure that the scan only checks newly installed files.
Correct.
Only new
On Wednesday October 22 2014 16:08:16 Jeremy Lavergne wrote:
Just because something installed doesn't mean it actually built correctly...
I'd put it this way: just because something built and installed doesn't mean
that it installed correctly (thinking of the recent re-discussion about
On Oct 22, 2014, at 3:47 PM, Arno Hautala a...@alum.wpi.edu wrote:
You could disable the scan with --no-rev-upgrade and run the command on its
own (port rev-upgrade) once you're done installing ports; continuing your
real work in another window.
You could also set revupgrade_autorun to no
Short version: updated to MacPorts 2.3.2 for the same reason that Everest
was climbed, but forewarned by the iOS 8 debacle I held off with Yosemite
for a while because it needed Xcode 6.1.
Well, it just made itself at home; I've yet to venture into ports-land...
--
Dave Horsfall (VK2KFU)
On Oct 22, 2014, at 4:24 PM, James Berry jbe...@macports.org wrote:
On Oct 22, 2014, at 1:06 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Wednesday October 22 2014 15:51:38 Jeremy Lavergne wrote:
On Oct 22, 2014, at 3:47 PM, Arno Hautala wrote:
I'm pretty sure that the scan only checks
On Wed, Oct 22, 2014 at 5:46 PM, William H. Magill mag...@mac.com wrote:
1- This release of OSX TIGHTLY integrates local I/O with iCloud (i.e.
network) I/O. This implies that there was probably some significant work
done in the Kernel Level I/O routines.
I am under the impression that this
On Oct 22, 2014, at 5:53 PM, Brandon Allbery allber...@gmail.com wrote:
On Wed, Oct 22, 2014 at 5:46 PM, William H. Magill mag...@mac.com wrote:
1- This release of OSX TIGHTLY integrates local I/O with iCloud (i.e.
network) I/O. This implies that there was probably some significant work
On Oct 22, 2014, at 3:06 PM, René J.V. Bertin wrote:
On Wednesday October 22 2014 15:51:38 Jeremy Lavergne wrote:
On Oct 22, 2014, at 3:47 PM, Arno Hautala wrote:
I'm pretty sure that the scan only checks newly installed files.
Correct.
Only new (yet-to-be-scanned) files get added,
On Wednesday October 22 2014 18:00:29 Lawrence Velázquez wrote:
For instance, the boot volume is converted to a Core Storage logical volume
on upgrade.
I know it's off-topic, but what on earth does that mean?
R
___
macports-users mailing list
http://en.wikipedia.org/wiki/Logical_volume_management
On Oct 22, 2014, at 6:42 PM, René J.V. Bertin wrote:
For instance, the boot volume is converted to a Core Storage logical volume
on upgrade.
I know it's off-topic, but what on earth does that mean?
On Oct 22, 2014, at 6:42 PM, René J.V. Bertin rjvber...@gmail.com wrote:
On Wednesday October 22 2014 18:00:29 Lawrence Velázquez wrote:
For instance, the boot volume is converted to a Core Storage logical volume
on upgrade.
I know it's off-topic, but what on earth does that mean?
In
19 matches
Mail list logo
