> On Jan 10, 2015, at 18:51, Ryan Schmidt wrote:
>
>
>> On Jan 10, 2015, at 2:53 PM, jerem...@macports.org wrote:
>>
>> Revision
>> 131393
>> Author
>> jerem...@macports.org
>> Date
>> 2015-01-10 12:53:49 -0800 (Sat, 10 Jan 2015)
>> Log Message
>>
>> clang-3.5: Build fix for Leopard
>
>> Mod
> On Jan 10, 2015, at 2:53 PM, jerem...@macports.org wrote:
>
> Revision
> 131393
> Author
> jerem...@macports.org
> Date
> 2015-01-10 12:53:49 -0800 (Sat, 10 Jan 2015)
> Log Message
>
> clang-3.5: Build fix for Leopard
> Modified: trunk/dports/lang/llvm-3.5/Portfile (131392 => 131393)
> -
On 2015-1-11 13:17 , Ryan Schmidt wrote:
> On Jan 10, 2015, at 7:18 PM, Clemens Lang wrote:
>
>> I'd argue for reducing the frequency at which VACUUM is run (for example
>> until
>> a certain threshold of free pages is reached) and adding output indicating
>> that
>> MacPorts is doing some clean
On Jan 10, 2015, at 7:18 PM, Clemens Lang wrote:
> I'd argue for reducing the frequency at which VACUUM is run (for example until
> a certain threshold of free pages is reached) and adding output indicating
> that
> MacPorts is doing some cleanup work.
>
Yes, having indication -- separate from
On 11.01.2015 02:18 AM, Clemens Lang wrote:
> I'd argue for reducing the frequency at which VACUUM is run (for example until
> a certain threshold of free pages is reached) and adding output indicating
> that
> MacPorts is doing some cleanup work.
rand(10) == 6?
signature.asc
Description: Open
Hi,
- On 10 Jan, 2015, at 23:45, René J.V. Bertin rjvber...@gmail.com wrote:
> Those don't even post a message saying that the actual work they do happens in
> the background, only the manpage suggests to monitor the database server
> process to know when the fsck/vacuum'ing is finished. If M
On Saturday January 10 2015 17:14:48 Lawrence Velázquez wrote:
> Do you expect a command-line foreground job to spawn background jobs that
> continue after the foreground job has finished? I sure don't. And such
> behavior would give a false impression that port(1) is finished, when it
> actual
On 2015-1-11 08:50 , René J.V. Bertin wrote:
>>> MacPorts does not currently have any background processes; adding one would
>>> be a major change.
>>
>> This would also only be useful if there were something else MacPorts could
>> be doing at the same time in the foreground. I think it would be
On Jan 10, 2015, at 4:50 PM, René J.V. Bertin wrote:
> I don't see what's confusing when a process that most users don't know (nor
> care) about keeps running. All they notice is that the port command
> terminates a bit earlier than before.
Do you expect a command-line foreground job to spawn
> > MacPorts does not currently have any background processes; adding one would
> > be a major change.
>
> This would also only be useful if there were something else MacPorts could be
> doing at the same time in the foreground. I think it would be confusing to
> add some sort of vacuum process
> On Jan 10, 2015, at 9:58 AM, Joshua Root wrote:
>
> On 2015-1-11 00:18 , Clemens Lang wrote:
>>
>>
>> - On 10 Jan, 2015, at 12:28, Mojca Miklavec mo...@macports.org wrote:
>>
>>> I already mentioned a while ago some annoying behaviour of macports:
>>> sudo port uninstall
>>> (maybe a
On Jan 10, 2015, at 1:53 PM, Ryan Schmidt wrote:
> On Jan 10, 2015, at 12:05 PM, René J.V. Bertin wrote:
>
>> But how about moving the task to a background process?
>
> MacPorts does not currently have any background processes; adding one would
> be a major change.
This would also only be use
On Jan 10, 2015, at 12:05 PM, René J.V. Bertin wrote:
> But how about moving the task to a background process?
MacPorts does not currently have any background processes; adding one would be
a major change.
___
macports-dev mailing list
macports-dev@
On 2015-1-11 00:18 , Clemens Lang wrote:
>
>
> - On 10 Jan, 2015, at 12:28, Mojca Miklavec mo...@macports.org wrote:
>
>> I already mentioned a while ago some annoying behaviour of macports:
>>sudo port uninstall
>> (maybe also sudo clean) sometimes takes forever. I can uninstall 10
>>
> On Oct 5, 2014, at 9:10 PM, khindenb...@macports.org wrote:
>
> Revision
> 126240
> Author
> khindenb...@macports.org
> Date
> 2014-10-05 19:10:39 -0700 (Sun, 05 Oct 2014)
> Log Message
>
> gradle-devel: obsolete - this version is older than gradle and no maintainer
> Modified: trunk/dports/d
On Jan 10, 2015, at 6:45 AM, René J.V. Bertin wrote:
> NB: one way to speed up things at least as far as user experience goes is
> postponing the clean step to the end in things like `port upgrade outdated`,
> and relegating them to a background process if that's possible. It's a bit
> tricky
> On Jan 9, 2015, at 10:19 PM, ebori...@macports.org wrote:
>
> Revision
> 131336
> Author
> ebori...@macports.org
> Date
> 2015-01-09 20:19:30 -0800 (Fri, 09 Jan 2015)
> Log Message
>
> hdf5-lz4-plugin: New port; adds lz4 de/compressor as plugin to HDF5.
> Added: trunk/dports/science/hdf5-lz4-
- On 10 Jan, 2015, at 12:28, Mojca Miklavec mo...@macports.org wrote:
> I already mentioned a while ago some annoying behaviour of macports:
>sudo port uninstall
> (maybe also sudo clean) sometimes takes forever. I can uninstall 10
> ports, but the time won't multiply by 10, it seems th
> On Jan 10, 2015, at 5:38 AM, vi...@macports.org wrote:
>
> Revision
> 131354
> Author
> vi...@macports.org
> Date
> 2015-01-10 03:38:40 -0800 (Sat, 10 Jan 2015)
> Log Message
>
> cgal: bumps to 4.5.1
> Modified Paths
>
> • trunk/dports/gis/cgal/Portfile
> Diff
>
> Modified: trunk/dport
Hi,
I already mentioned a while ago some annoying behaviour of macports:
sudo port uninstall
(maybe also sudo clean) sometimes takes forever. I can uninstall 10
ports, but the time won't multiply by 10, it seems that there's only a
single very time consuming step somewhere in the process, but
20 matches
Mail list logo
