On 2013-10-29 14:36 , Mark Anderson wrote:
> What's the status of Macports_Framework? I was looking in SVN and the
> last commit was 6 years ago. I was looking to work on it, is that the
> latest?
I haven't tried it lately, but there have definitely been commits more
recently than that, r102779 be
What's the status of Macports_Framework? I was looking in SVN and the last
commit was 6 years ago. I was looking to work on it, is that the latest?
—Mark
___
Mark E. Anderson
___
macports-dev mailing list
macports-dev@lists.macosforg
On Oct 28, 2013, at 5:34 PM, James Berry wrote:
>
> On Oct 28, 2013, at 5:12 PM, Ned Deily wrote:
>
>> In article ,
>> Ryan Schmidt wrote:
>>> If you do that, make sure you only print that on Mavericks and later, since
>>> on earlier OS versions tclConfig.sh is not part of the command line
On Oct 28, 2013, at 5:12 PM, Ned Deily wrote:
> In article ,
> Ryan Schmidt wrote:
>> If you do that, make sure you only print that on Mavericks and later, since
>> on earlier OS versions tclConfig.sh is not part of the command line tools
>> and
>> it should already be there out of the box.
In article ,
Ryan Schmidt wrote:
> If you do that, make sure you only print that on Mavericks and later, since
> on earlier OS versions tclConfig.sh is not part of the command line tools and
> it should already be there out of the box.
AFAIK, (and I just checked on a vanilla 10.8.5 system that
Requesting the following diffs/patches be reviewed/committed.
- #39751 devel/check
- maintainer timeout/openmaintainer
- 4 months since initial request
- 4 days since my latest patch update (not required but cleaner)
- #40876 devel/libcurvecpr
- Submission, same vein as
On Oct 28, 2013, at 15:27, Michael Dickens wrote:
> The current "Mavericks Problems" MacPorts Wiki page, <
> https://trac.macports.org/wiki/MavericksProblems> in the "Updating
> MacPorts Base" section says:
>
> {{{
> Ensure you have at least the command line tools installed by running
> xcode-se
The current "Mavericks Problems" MacPorts Wiki page, <
https://trac.macports.org/wiki/MavericksProblems> in the "Updating
MacPorts Base" section says:
{{{
Ensure you have at least the command line tools installed by running
xcode-select --install from a Terminal. Make sure to also run this even
if
On Oct 28, 2013, at 09:05, rai...@macports.org wrote:
> Revision
> 112625
> Author
> rai...@macports.org
> Date
> 2013-10-28 07:05:24 -0700 (Mon, 28 Oct 2013)
> Log Message
>
> editors/MacVim:
> Switch livecheck URL to tagged releases as the homepage was not updated
>
> Modified Paths
>
>
On 2013-10-26 09:13, Ryan Schmidt wrote:
> Can’t nls be on all the time, like it is in most other ports? Why make it a
> variant?
No particular reason, I just thought I would provide it this way. Now I
see that +nls is not common at all, so I will just remove this variant
and include localization
On Oct 27, 2013, at 16:05, take...@macports.org wrote:
> Revision
> 112605
> Author
> take...@macports.org
> Date
> 2013-10-27 14:05:19 -0700 (Sun, 27 Oct 2013)
> Log Message
>
> blahtexml: added patches to fix build
> --- trunk/dports/tex/blahtexml/Portfile 2013-10-27 20:51:52 UTC (rev
11 matches
Mail list logo
