Hi
For testing it should be enough to just modify the registry.db locally
> as you need it. Once you reach a stable schema, you will have to add
> modifications to the registry schema at two places.
>
> 1) The initial database schema for new installations is defined here:
>
>
Hi
> I have not followed Rainer's strategy for having `port snapshot --create`
> and `port snapshot --restore` as discussed in the previous thread, instead
> have 3 separate actions...
>
> If I am following this correctly I think isolating the functionality into
> actions makes sense. If we want
On 2017-06-13, at 4:20 PM, Joshua Root wrote:
> On 2017-6-14 08:18 , Christopher Jones wrote:
>> Had a look into this. The ROOT source never explicitly opens /dev/random in
>> read/write mode. Only read only.
>> However, it also uses a number of external library calls, like
On 2017-6-14 08:18 , Christopher Jones wrote:
Had a look into this. The ROOT source never explicitly opens /dev/random in
read/write mode. Only read only.
However, it also uses a number of external library calls, like std::rand(), and
my best bet is one of these is doing it. As writing to
Hi,
turning off the sandbox fixed the build, so this definitely is the issue….
I agree requiring access to /dev/random during the build is a bit weird, but
actually does make some sense in this case, the script being run is generating
an example output ROOT file for the tutorials, which
On 2017-6-14 07:05 , Daniel J. Luke wrote:
On Jun 13, 2017, at 4:57 PM, Christopher Jones wrote:
:info:build open('/dev/random'): Operation not permitted
Now, this works outside. So I suspect the build is in some way prevent the
build process from accessing this. Is
On Jun 13, 2017, at 4:57 PM, Christopher Jones wrote:
> :info:build open('/dev/random'): Operation not permitted
>
> Now, this works outside. So I suspect the build is in some way prevent the
> build process from accessing this. Is this possible ? If so, more to the
>
Is this trace mode?
-Sterling
- Original Message -
From: "Christopher Jones"
To: "MacPorts Developers"
Sent: Tuesday, June 13, 2017 1:57:57 PM
Subject: Are macports builds prevented from accessing /dev/random ?
Hi,
I have a
> On Jun 13, 2017, at 03:52, Dan Villiom Podlaski Christiansen
> wrote:
>
> Dan Villiom Podlaski Christiansen (danchr) pushed a commit to branch master
> in repository macports-ports.
>
>
>
> On Feb 18, 2017, at 17:29, Dan Villiom Podlaski Christiansen
> wrote:
>
> Dan Villiom Podlaski Christiansen (danchr) pushed a commit to branch master
> in repository macports-ports.
>
>
>
10 matches
Mail list logo