Hi,
> I would like to see the time for each run (if 10 runs, then 10 columns
> i.e., xx_run1, xx_run2, ...), rather than only average of them.
>
> Collect as much as insights we could, maybe we find some pattern or
> something that might help us (not sure what though). Since I have a
> feeling, w
Hi,
>
> The database lives on disk in ${portdbpath}/registry/registry.db. It has
> to, or we wouldn't have the D in ACID [1].
>
>
Probably then it should make a huge difference in hdd or fusion drives. All
tests I made were on ssd.
Also I tried connecting an external hdd, but when I tried installi
Hi,
As a quick feedback: Gitter doesn't seem to be mature enough, so that
those of us who kept testing it (for about three weeks) would want to
use it in the long run.
* The Android app constantly keeps crashing.
* Even if it is not crashing, I wasn't able to configure it to get
notifications whe
> On Jun 12, 2019, at 4:47 PM, Bruce R Miller via macports-dev
> wrote:
>
> So, I tracked it down to the Makefile that perl's MakeMaker generates;
> an innocuous thing called "fixin" does that substitution.
Possibly related: it is a known issue in MakeMaker that `#!/usr/bin/env perl`
in scr
On 6/12/19 3:06 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 13:41, Bruce R Miller wrote:
On 6/12/19 1:14 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
So, apparently the perl portgroup replaces shebang
lines that it recognizes with a call to the specific
perl that wa
On Sun, Jun 9, 2019 at 6:01 PM Mihir Luthra <1999mihir.lut...@gmail.com> wrote:
>
> Hi jan,
>
>>
>> How exactly were these numbers obtained? Is it one run?
>> An average of ten runs? All following a complete distclean?
>> Is it the "real" time as reported by time(1) or somethin else?
>> What are th
On Jun 12, 2019, at 13:41, Bruce R Miller wrote:
> On 6/12/19 1:14 PM, Ryan Schmidt wrote:
>> On Jun 12, 2019, at 10:26, Bruce Miller wrote:
>>
>>> So, apparently the perl portgroup replaces shebang
>>> lines that it recognizes with a call to the specific
>>> perl that was specified in the portfi
On 6/12/19 1:14 PM, Ryan Schmidt wrote:
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
So, apparently the perl portgroup replaces shebang
lines that it recognizes with a call to the specific
perl that was specified in the portfile (? is that right?)
And if so, it doesn't recognize the above lin
On Jun 12, 2019, at 10:26, Bruce Miller wrote:
> [This is motivated by the LaTeXML port,
> but is a general question about perl portgroup]
>
> A colleague suggested the clever shebang line
> #!/usr/bin/env perl
> as a way to easily allow testing against different
> versions of perl, running i
* Bruce Miller:
> (And ideally, I'd avoid the whole version business, since LaTeXML
> *should* work with any version of perl after, I think, 5.10)
If you are able to determine a minimum required Perl version 5.x.y,
might adding 'use 5.x.y;' (e.g. via a patch) for a compile time version
check solv
[This is motivated by the LaTeXML port,
but is a general question about perl portgroup]
A colleague suggested the clever shebang line
#!/usr/bin/env perl
as a way to easily allow testing against different
versions of perl, running in sandboxes, etc.
This has worked fine on all systems, so far,
On 2019-6-12 14:17 , Mihir Luthra wrote:
> hi,
>
> i just wanted to ask a small question.
> Is the sqlite3 database used in macports in memory? I don't have a nice
> knowledge about databases. The main question concerning me is the time
> taken by darwintrace calls to tracelib and querying of regi
12 matches
Mail list logo
