On Jan 16, 2013, at 00:21, Eric A. Borisch wrote:
> On Tuesday, January 15, 2013, Ryan Schmidt wrote:
>
>> It can't be changed for py-spyder-devel now, but for other ports in the
>> future, please just increase the epoch by one when it's needed. There's no
>> reason for the epoch to be formatt
On Jan 15, 2013, at 11:18 PM, Sean Farley >
wrote:
How and when is the csearch index updated? I like that grep gets me
completely up-to-date results every time.
>>>
>>> It's manual but cindex updates itself in ~7s (depending on the number
>>> of changed files) for me and is more than just mac
Any thoughts on performing the man page (re)compression in parallel
(multiple jobs)? It seems like reasonably low-hanging fruit, and on a port
with lots of man pages, it can take a while. Not gobs of time, mind you,
but enough to make me ask the question.
Thanks,
Eric
--
Eric A. Borisch
_
01627)
> > @@ -3,8 +3,9 @@
> >
> > PortSystem 1.0
> > namepy-spyder-devel
> > -version 2.2.0-dev
> > +version 2.2.0beta1
> > revision0
> > +epoch 20130115
>
> It can'
On Jan 14, 2013, at 19:55, dev...@macports.org wrote:
> Revision: 101612
> https://trac.macports.org/changeset/101612
> Author: dev...@macports.org
> Date: 2013-01-14 17:55:31 -0800 (Mon, 14 Jan 2013)
> Log Message:
> ---
> cogl: new port, a hardware accelerated 3D graphics
On Jan 14, 2013, at 19:57, dev...@macports.org wrote:
> Revision: 101613
> https://trac.macports.org/changeset/101613
> Author: dev...@macports.org
> Date: 2013-01-14 17:57:43 -0800 (Mon, 14 Jan 2013)
> Log Message:
> ---
> clutter: update to version 1.12.2, update dependen
ev
> +version 2.2.0beta1
> revision0
> +epoch 20130115
It can't be changed for py-spyder-devel now, but for other ports in the future,
please just increase the epoch by one when it's needed. There's no reason for
the epoch to be f
On Tue, Jan 15, 2013 at 11:10 PM, Ryan Schmidt wrote:
> On Jan 15, 2013, at 23:02, Sean Farley wrote:
>> On Tue, Jan 15, 2013 at 10:48 PM, Ryan Schmidt wrote:
>>> On Jan 15, 2013, at 13:17, Sean Farley wrote:
For me, this command takes:
$ time find $MP/dports -maxdepth 3 -name Portf
On Jan 15, 2013, at 23:10, Blair Zajac wrote:
> I used the find | cpio approach in
>
> https://trac.macports.org/changeset/101649 and
> https://trac.macports.org/changeset/101650
>
> I spent a bunch of time trying different approaches and the committed
> approach looks to be the best. It does
On Tue, Jan 15, 2013 at 11:10 PM, Blair Zajac wrote:
> On 01/14/2013 08:32 PM, Blair Zajac wrote:
>>
>> On 01/14/2013 05:33 PM, Sean Farley wrote:
>>>
>>> On Mon, Jan 14, 2013 at 11:09 AM, Blair Zajac wrote:
On 01/13/2013 06:46 PM, Ryan Schmidt wrote:
>
>
>
> On Jan 13,
On Jan 15, 2013, at 23:02, Sean Farley wrote:
> On Tue, Jan 15, 2013 at 10:48 PM, Ryan Schmidt wrote:
>> On Jan 15, 2013, at 13:17, Sean Farley wrote:
>>> For me, this command takes:
>>>
>>> $ time find $MP/dports -maxdepth 3 -name Portfile -exec echo {} \;
>>> -exec grep -E -- "AUTHORS" {} \; | g
On 01/14/2013 08:32 PM, Blair Zajac wrote:
On 01/14/2013 05:33 PM, Sean Farley wrote:
On Mon, Jan 14, 2013 at 11:09 AM, Blair Zajac wrote:
On 01/13/2013 06:46 PM, Ryan Schmidt wrote:
On Jan 13, 2013, at 18:53, Blair Zajac wrote:
On 01/13/2013 03:36 PM, Ryan Schmidt wrote:
https://trac.m
On Tue, Jan 15, 2013 at 10:48 PM, Ryan Schmidt wrote:
>
> On Jan 15, 2013, at 11:48, Sean Farley wrote:
>
>> 1) The gap between Trac and the mailing lists is huge. Sometimes there
>> are long discussion on Trac that I completely miss since they don't
>> happen on the mailing list. My question is h
On Jan 15, 2013, at 11:48, Sean Farley wrote:
> 1) The gap between Trac and the mailing lists is huge. Sometimes there
> are long discussion on Trac that I completely miss since they don't
> happen on the mailing list. My question is how could we close this
> gap?
The Subversion project has a st
On 2013-1-16 09:22 , Lawrence Velázquez wrote:
> On Jan 15, 2013, at 5:05 PM, Sean Farley wrote:
>
>> I'm looking for advice / best practices for bypassing the extract
>> phase when writing a portfile for a script (and hence it's not a
>> tarball). One idea I had was something like the following,
On Jan 15, 2013, at 03:43, Lawrence Velázquez wrote:
> It also wouldn't work for any Portfiles that had some sort of custom
> modeline. Are there any of those?
I would certainly prefer if all portfiles had the same modeline.
___
macports-dev mailin
On Jan 15, 2013, at 16:05, Sean Farley wrote:
> I'm looking for advice / best practices for bypassing the extract
> phase when writing a portfile for a script (and hence it's not a
> tarball). One idea I had was something like the following,
>
> {{{
> distname${name}
> extract.suffix
On Jan 15, 2013, at 5:05 PM, Sean Farley wrote:
> I'm looking for advice / best practices for bypassing the extract
> phase when writing a portfile for a script (and hence it's not a
> tarball). One idea I had was something like the following,
>
> {{{
> distname${name}
> extract.suff
Hi list,
I'm looking for advice / best practices for bypassing the extract
phase when writing a portfile for a script (and hence it's not a
tarball). One idea I had was something like the following,
{{{
distname${name}
extract.suffix
use_configure no
extract {}
buil
In article <50f5b8ce.6000...@wu.ac.at>,
Gustaf Neumann wrote:
> For me, the following ports fail currently due to using Tcl8.6 in the
> port "tcl".
>
> expect
> libnewt
> zebra
> xotcl
Another data point from an observer: as I've mentioned before, AFAIK
upstream Python has had little exposure
On Tue, Jan 15, 2013 at 2:55 PM, Lawrence Velázquez wrote:
> On Jan 15, 2013, at 12:48 PM, Sean Farley wrote:
>
>> 2) Patch review? Sometimes I have questions on how to do a particular
>> task (i.e. best practice for "extracting" a script that isn't zipped?)
>> but can't figure it out by looking
In article
,
Sean Farley wrote:
> On Tue, Jan 15, 2013 at 1:28 PM, Bradley Giesbrecht
> wrote:
> >
> > On Jan 15, 2013, at 11:17 AM, Sean Farley wrote:
> >
> >> On Tue, Jan 15, 2013 at 12:03 PM, Bradley Giesbrecht
> >> wrote:
[...]
> >>> Do you subscribe to these lists?
> >>> macports-tick...@
On Jan 15, 2013, at 12:48 PM, Sean Farley wrote:
> 2) Patch review? Sometimes I have questions on how to do a particular
> task (i.e. best practice for "extracting" a script that isn't zipped?)
> but can't figure it out by looking at other portfiles mostly due to
> the fact that it's not commonly
On 15/gen/2013, at 21:18, Chris Jones wrote:
> Hi,
>
> On 15 Jan 2013, at 8:01pm, Aljaž Srebrnič wrote:
>
>> On 15/gen/2013, at 20:55, Chris Jones wrote:
>>
>> Yeah, honestly I don't even remember why I enabled all of them. :D I enabled
>> qt4_mac to test it out, so I wouldn't have x11 star
Hi,
On 15 Jan 2013, at 8:01pm, Aljaž Srebrnič wrote:
> On 15/gen/2013, at 20:55, Chris Jones wrote:
>
>>
>> On 15 Jan 2013, at 7:46pm, Aljaž Srebrnič wrote:
>>
>>> On 15/gen/2013, at 20:45, Chris Jones wrote:
>>>
Hi,
OK… so is that all of them ;)
>>>
>>> When I buil
On Jan 15, 2013, at 2:33 PM, Aljaž Srebrnič wrote:
> Oh, that, too :) I'll try to close some old ones when I have some time then!
Great idea! How about starting with this one?
https://trac.macports.org/ticket/126
vq
___
macports-dev mailing list
ma
Dear all,
For me, the following ports fail currently due to using Tcl8.6 in the
port "tcl".
expect
libnewt
zebra
xotcl
in addition some of my own ports (not yet submitted). For xotcl, the
proper tcl8.6 support is in nsf (supporting the NRE functionality; nsf
is still in beta; see http://nex
On 15/gen/2013, at 20:55, Chris Jones wrote:
>
> On 15 Jan 2013, at 7:46pm, Aljaž Srebrnič wrote:
>
>> On 15/gen/2013, at 20:45, Chris Jones wrote:
>>
>>> Hi,
>>>
>>>
>>> OK… so is that all of them ;)
>>
>> When I build, I build all-in ;)
>
> Fair enough in general. ROOT though has a hel
On 15 Jan 2013, at 7:46pm, Aljaž Srebrnič wrote:
> On 15/gen/2013, at 20:45, Chris Jones wrote:
>
>> Hi,
>>
>>> Nope, I built root this morning but I deleted the logs; I'm building now,
>>> will attach as soon as it finishes.
>>>
Builds fine for me on 10.8 + Xcode 4.5.2 …. What platfor
On Tue, Jan 15, 2013 at 1:28 PM, Bradley Giesbrecht
wrote:
>
> On Jan 15, 2013, at 11:17 AM, Sean Farley wrote:
>
>> On Tue, Jan 15, 2013 at 12:03 PM, Bradley Giesbrecht
>> wrote:
>>>
>>> On Jan 15, 2013, at 9:48 AM, Sean Farley wrote:
>>>
On Mon, Jan 14, 2013 at 2:18 AM, rod wrote:
> H
On 15 Jan 2013, at 7:39pm, Chris Jones wrote:
>
> On 15 Jan 2013, at 7:32pm, Aljaž Srebrnič wrote:
>
>> On 15/gen/2013, at 18:56, Chris Jones wrote:
>>
>>> Hi,
>>>
>>> Could a commuter take a look at
>>>
>>> https://trac.macports.org/ticket/37643
>>>
>>> ? Normally I wouldn't send an ema
On 15/gen/2013, at 20:39, Chris Jones wrote:
>
> On 15 Jan 2013, at 7:32pm, Aljaž Srebrnič wrote:
>
>> On 15/gen/2013, at 18:56, Chris Jones wrote:
>>
>>> Hi,
>>>
>>> Could a commuter take a look at
>>>
>>> https://trac.macports.org/ticket/37643
>>>
>>> ? Normally I wouldn't send an email
On Jan 15, 2013, at 11:17 AM, Sean Farley wrote:
> On Tue, Jan 15, 2013 at 12:03 PM, Bradley Giesbrecht
> wrote:
>>
>> On Jan 15, 2013, at 9:48 AM, Sean Farley wrote:
>>
>>> On Mon, Jan 14, 2013 at 2:18 AM, rod wrote:
Hi!
I've been finding developing and especially updating Po
On Tue, Jan 15, 2013 at 12:03 PM, Bradley Giesbrecht
wrote:
>
> On Jan 15, 2013, at 9:48 AM, Sean Farley wrote:
>
>> On Mon, Jan 14, 2013 at 2:18 AM, rod wrote:
>>> Hi!
>>>
>>> I've been finding developing and especially updating Portfiles a bit tricky
>>> and error prone, so have been writing so
On Jan 15, 2013, at 9:48 AM, Sean Farley wrote:
> On Mon, Jan 14, 2013 at 2:18 AM, rod wrote:
>> Hi!
>>
>> I've been finding developing and especially updating Portfiles a bit tricky
>> and error prone, so have been writing some tools for myself to help with
>> this...
>>
>> https://github.com
Hi,
Could a commuter take a look at
https://trac.macports.org/ticket/37643
? Normally I wouldn't send an email so soon after committing, but it turns out
this update fixes a 'seg. fault on quit' bug 5.34.03 suffered from, so it would
be good to get it out.
cheers Chris
smime.p7s
Description:
On Mon, Jan 14, 2013 at 2:18 AM, rod wrote:
> Hi!
>
> I've been finding developing and especially updating Portfiles a bit tricky
> and error prone, so have been writing some tools for myself to help with
> this...
>
> https://github.com/rodnaph/pearl
> https://github.com/rodnaph/ghsum
Neato.
>
On Jan 14, 2013, at 4:14 PM, Lawrence Velázquez wrote:
> Could mpvim set "nomodeline" and set the options (fileencoding, expandtab,
> etc.) itself?
Alright, time to set Aljaž right.
https://trac.macports.org/changeset/101624
Now mpvim just ignores the modeline and sets the appropriate buffer-
On Jan 11, 2013, at 16:08, Aljaž Srebrnič wrote:
> On 11/gen/2013, at 15:25, Jack Howarth wrote:
>
>> ps So far the main blocker in my packages is ccpnmr. It rebuilds without
>> error
>> under the new tcl/tk but crashes with an X windows rendering error (which
>> I'll
>> have to repost later).
On Jan 14, 2013, at 12:35, Clemens Lang wrote:
> On Mon, Jan 14, 2013 at 01:02:39AM -0600, Ryan Schmidt wrote:
>> I was under the impression that the reason the nodejs ports don't
>> support PowerPC is because v8 doesn't support PowerPC. (The comment in
>> the nodejs port reads "# V8 only support
On Jan 15, 2013, at 03:14, Aljaž Srebrnič wrote:
> I was poking around on Trac tying to find an excuse for not studying and
> found out that there are 1091 tickets open but older than a year[1]. So, what
> about choosing a date and have a big meetup on IRC and close some tickets? :)
No need to
41 matches
Mail list logo
