On 2016-10-21 01:42 , Lawrence Velázquez wrote:
On Oct 20, 2016, at 3:40 AM, René J.V. Bertin wrote:
On Wednesday October 19 2016 21:44:04 Ryan Schmidt wrote:
No, that situation should not be common, nor indeed present at all.
I'm not sure I agree. PortGroups are intended to take care of se
> On Oct 20, 2016, at 6:58 PM, Ryan Schmidt wrote:
>
> Are the passwords then a separate entry?
I overlooked passwords; I'll have to chew on that.
> I had planned to put the guide-building and www-fetching and
> ports-sql-updating and distfiles-fetching and rsync-server-updating
> tasks on the
> On Oct 20, 2016, at 5:24 PM, Lawrence Velázquez wrote:
>
>> On Sep 12, 2016, at 9:06 PM, Ryan Schmidt wrote:
>>
>>> On Sep 12, 2016, at 7:46 AM, Rainer Müller wrote:
>>>
On 2016-09-12 04:17, Ryan Schmidt wrote:
There are currently too many places in master.cfg that have
>>>
> On Sep 12, 2016, at 9:06 PM, Ryan Schmidt wrote:
>
>> On Sep 12, 2016, at 7:46 AM, Rainer Müller wrote:
>>
>>> On 2016-09-12 04:17, Ryan Schmidt wrote:
>>>
>>> There are currently too many places in master.cfg that have
>>> knowledge of which worker runs on which platform. I'd like to get
>>
On 10/20/2016 10:25 PM, René J.V. Bertin wrote:
> On Thursday October 20 2016 15:38:42 Lawrence Velázquez wrote:
>
>> Better that than increasing the complexity of base and portfiles.
>
> Yeah, unless someone proposes to implement something in a portgroup. Then all
> of a sudden it becomes base
> On Oct 20, 2016, at 4:25 PM, René J.V. Bertin
> wrote:
>
>> On Thursday October 20 2016 15:38:42 Lawrence Velázquez wrote:
>>
>> Better that than increasing the complexity of base and portfiles.
>
> Yeah, unless someone proposes to implement something in a portgroup.
> Then all of a sudden it
On Thursday October 20 2016 15:38:42 Lawrence Velázquez wrote:
> Better that than increasing the complexity of base and portfiles.
Yeah, unless someone proposes to implement something in a portgroup. Then all
of a sudden it becomes base functionality ...
I won't be reinventing all kinds of whee
> On Oct 20, 2016, at 3:34 PM, René J.V. Bertin wrote:
>
> On Thursday October 20 2016 10:42:09 Lawrence Velázquez wrote:
>
>> It is already possible to create options that enable/disable portgroup
>> behavior after the portgroup is included. The python-1.0 and php-1.1 do
>
> Which increases th
On Thursday October 20 2016 10:42:09 Lawrence Velázquez wrote:
> It is already possible to create options that enable/disable portgroup
> behavior after the portgroup is included. The python-1.0 and php-1.1 do
Which increases the implementation complexity of the portgroup - each portgroup
that n
> On 20 Oct 2016, at 21:12, Lawrence Velázquez wrote:
>>
>> Yeah, I get that, but I mean: so nothing has changed yet: SVN is still
>> supposed to work the way it always did (at least to my knowledge).
>
> Right.
Thanks! I get out of your hair.
V.
> On Oct 20, 2016, at 2:47 PM, Vincent Habchi wrote:
>
>> On 20 Oct 2016, at 20:44, Rainer Müller wrote:
>> No, this downtime is not intentional or planned.
>
> Yeah, I get that, but I mean: so nothing has changed yet: SVN is still
> supposed to work the way it always did (at least to my knowl
> On 20 Oct 2016, at 20:44, Rainer Müller wrote:
> No, this downtime is not intentional or planned.
Yeah, I get that, but I mean: so nothing has changed yet: SVN is still supposed
to work the way it always did (at least to my knowledge).
Thanks!
V.
On 2016-10-20 20:28, Vincent Habchi wrote:
>> On 20 Oct 2016, at 14:04, Ryan Schmidt wrote:
>> Trac, svn, www-origin and guide-origin are inaccessible outside of the Apple
>> network. I'm trying to figure out why.
>
> I’ve been very busy lately and didn’t have much time but for very perfunctory
That's not really a reduced test case. It would be helpful if we could get a
reduced test case of the problem that doesn't involve having to debug the
entire guile application. An ideal test case would be a small C or C++ file
without external dependencies that showcased the issue.
--Jeremy
Hey,
> On 20 Oct 2016, at 14:04, Ryan Schmidt wrote:
>
>> On Oct 20, 2016, at 6:48 AM, Peter Danecek wrote:
>>
>> Hi all,
>> I am current not able to reach the trac server. Is this a real issue, or
>> just a local problem here?
>
> Trac, svn, www-origin and guide-origin are inaccessible outs
On Sun, Oct 9, 2016 at 3:20 PM, Jeremy Huddleston Sequoia
wrote:
>
>> On Oct 9, 2016, at 09:47, Jack Howarth wrote:
>>
>> On Sun, Oct 9, 2016 at 3:53 AM, Jeremy Huddleston Sequoia
>> wrote:
>>> thread_local support was added in OS X 10.9 (along with __cxa_thread_atexit
>>> being added to Libc a
Le 20/10/2016 à 04:35, Ryan Schmidt a écrit :
>> +notes "
>> ++--- LORENE Usage note -
>> +| To compile LORENE code, you should run:
>> +| export HOME_LORENE=${prefix}/lib/lorene
>> +| Codes are provided in \$HOME_LORENE/Codes. To use them, copy
> On Oct 20, 2016, at 3:40 AM, René J.V. Bertin wrote:
>
>> On Wednesday October 19 2016 21:44:04 Ryan Schmidt wrote:
>>
>> No, that situation should not be common, nor indeed present at all.
>
> I'm not sure I agree. PortGroups are intended to take care of setting
> up things for the ports tha
> On Oct 20, 2016, at 6:48 AM, Peter Danecek wrote:
>
> Hi all,
> I am current not able to reach the trac server. Is this a real issue, or just
> a local problem here?
Trac, svn, www-origin and guide-origin are inaccessible outside of the Apple
network. I'm trying to figure out why.
___
Hi all,
I am current not able to reach the trac server. Is this a real issue, or just a
local problem here?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
> On 18 Oct 2016, at 06:47, Lawrence Velázquez wrote:
>
> Fred Wright recently opened several tickets that suggest restoring
> several Python subports that were deprecated and moved to the Python
> graveyard a long time ago.
>
> https://trac.macports.org/ticket/52636
> https://trac.macports.org
On 20 October 2016 at 04:42, Joshua Root wrote:
> On 2016-10-20 13:23 , Ryan Schmidt wrote:
>>
>>
>>> On Oct 19, 2016, at 9:04 PM, mo...@macports.org wrote:
>>>
>>> Revision
>>> 154081
>>> Author
>>> mo...@macports.org
>>> Date
>>> 2016-10-19 19:04:20 -0700 (Wed, 19 Oct 2016)
>>> Log Message
>>>
>
On Wednesday October 19 2016 21:44:04 Ryan Schmidt wrote:
>No, that situation should not be common, nor indeed present at all.
I'm not sure I agree. PortGroups are intended to take care of setting up things
for the ports that use them (like declaring a dependency in such a way ports
work with t
Hi,
Trac seems to be down for me at the moment.
I switched most of the ports to perl5.24, but there are some ports like
- cpuid
- docbook-utils
- pcsc-tools
that do just
PortGroup perl5 1.0
depends_build port:p${perl5.major}-foo
without specifying the perl version to use
24 matches
Mail list logo
