I know Yosemite is officially only a couple days old, but I was
wondering if a new build slave is on the schedule. I think I recall
hearing that they're all VMs now so setting up new versions should be
easier.
Thanks,
--Arno
--
arno s hautala/-| a...@alum.wpi.edu
pgp b2c9d448
At 12:45 PM +0200 10/18/14, Peter Danecek wrote:
On 18 Oct 2014, at 02:55, Craig Treleaven ctrelea...@macports.org wrote:
I've ended up with an svn conflict--just in the capitalization of
the directory name, if I'm reading this right.
SixBare:mp-trunk-ports craigtreleaven$ svn status
?
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0, remove py24, py25 subport
Perhaps we want to add them to py-graveyard?
On Oct 18, 2014, at 7:05 AM, take...@macports.org wrote:
Revision
126963
Author
take...@macports.org
Date
2014-10-18 05:05:00 -0700 (Sat, 18 Oct 2014)
Log Message
g95: blacklist clang on Lion and Mountain Lion
Modified Paths
• trunk/dports/lang/g95/Portfile
+if
On Oct 18, 2014, at 8:20 AM, Arno Hautala wrote:
I know Yosemite is officially only a couple days old, but I was
wondering if a new build slave is on the schedule. I think I recall
hearing that they're all VMs now so setting up new versions should be
easier.
We requested it at the beginning
On Oct 18, 2014, at 8:22 AM, Craig Treleaven wrote:
At 12:45 PM +0200 10/18/14, Peter Danecek wrote:
On 18 Oct 2014, at 02:55, Craig Treleaven wrote:
I've ended up with an svn conflict--just in the capitalization of the
directory name, if I'm reading this right.
SixBare:mp-trunk-ports
On Oct 16, 2014, at 10:42 AM, Brandon Allbery wrote:
This is just that these programs (in particular osacompile which is the
Applescript compiler) use the CFPreferences framework, which always looks for
stuff in $HOME before system locations, and for whatever reason the fake home
On 17 Oct 2014, at 22:26, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 17, 2014, at 1:33 PM, p...@macports.org wrote:
Revision
126921
Author
p...@macports.org
Date
2014-10-17 11:33:53 -0700 (Fri, 17 Oct 2014)
Log Message
py-tvdb: update to version 1.9, github portgroup,
At 10:59 AM -0500 10/18/14, Ryan Schmidt wrote:
On Oct 18, 2014, at 8:22 AM, Craig Treleaven wrote:
At 12:45 PM +0200 10/18/14, Peter Danecek wrote:
On 18 Oct 2014, at 02:55, Craig Treleaven wrote:
I've ended up with an svn conflict--just in the capitalization
of the directory name, if
On 18 Oct 2014, at 17:45, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0, remove py24, py25 subport
On Oct 18, 2014, at 11:18 AM, Craig Treleaven wrote:
At 10:59 AM -0500 10/18/14, Ryan Schmidt wrote:
$ port lint MacPorts_daemondo
--- Verifying Portfile for MacPorts_daemondo
Warning: Line 2 is missing RCS tag ($Id$)
Error: Portfile directory macports_daemondo does not match port name
On Oct 18, 2014, at 11:21 AM, petr wrote:
On 18 Oct 2014, at 17:45, Ryan Schmidt wrote:
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0,
On 2014-10-19 02:45 , Ryan Schmidt wrote:
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0, remove py24, py25 subport
Perhaps we want to add them to
On 2014-10-19 02:49 , Ryan Schmidt wrote:
On Oct 18, 2014, at 8:20 AM, Arno Hautala wrote:
I know Yosemite is officially only a couple days old, but I was
wondering if a new build slave is on the schedule. I think I recall
hearing that they're all VMs now so setting up new versions should
At 11:24 AM -0500 10/18/14, Ryan Schmidt wrote:
On Oct 18, 2014, at 11:18 AM, Craig Treleaven wrote:
At 10:59 AM -0500 10/18/14, Ryan Schmidt wrote:
$ port lint MacPorts_daemondo
--- Verifying Portfile for MacPorts_daemondo
Warning: Line 2 is missing RCS tag ($Id$)
Error: Portfile
Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either port A
or port B?
Mark
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On Oct 18, 2014, at 2:09 PM, Jeremy Lavergne jer...@lavergne.gotdns.org wrote:
Usually a variant or subport would achieve this.
On Oct 18, 2014, at 2:41 PM, Mark Brethen wrote:
Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
port A or port B?
Right, but I
You'd have it also share the variants/subport naming.
There's a portgroup for ensuring whether variants are selected:
https://trac.macports.org/browser/trunk/dports/_resources/port1.0/group/active_variants-1.1.tcl
On Oct 18, 2014, at 3:13 PM, Mark Brethen wrote:
Right, but I have subport C
On 18 Oct 2014, at 17:45, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0, remove py24, py25 subport
Dear Ryan and all,
This is unusual. What's the basis for this? Is it because of libstdc++? or
because of the clang version? or something else?
Thank you for noting this. This is not related to libstdc++ because g95 is
written in C.
Probably it is due to clang version.
Clang is somewhat
On 2014-10-19 08:08 , Takeshi Enomoto wrote:
fcomp is a comparison and a pop without a size, but
I'm not sure if I should add s (32-bit) or l (64-bit).
For example fmuls and movl are used before and after fcomp in line 412.
I don't speak assembler. Could anyone help me with asm?
Comments on
On Oct 18, 2014, at 12:33 PM, Craig Treleaven wrote:
Yes, you should fix the case of the directory. Since you have a
case-insensitive filesystem, you'll need to do the move in the repository,
rather than in your working copy:
https://subversion.apache.org/faq.html#case-change
In case
On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either port
A or port B?
No, unless port A and port B are different versions of the same software that
install their files to the same locations.
For example, if your port
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
port A or port B?
No, unless port A and port B are different versions of the same software
On Oct 18, 2014, at 7:19 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 7:16 PM, Mark Brethen wrote:
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
Is it possible to specify e.g lib-depends {port:A || port:B}
On Oct 18, 2014, at 7:32 PM, Mark Brethen wrote:
On Oct 18, 2014, at 7:19 PM, Ryan Schmidt wrote:
On Oct 18, 2014, at 7:16 PM, Mark Brethen wrote:
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
Is it possible to specify e.g
On Oct 18, 2014, at 9:09 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 7:32 PM, Mark Brethen wrote:
On Oct 18, 2014, at 7:19 PM, Ryan Schmidt wrote:
On Oct 18, 2014, at 7:16 PM, Mark Brethen wrote:
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
On Oct 18,
If B and C are different versions of the same program, for example a stable
version and a development version, then it is usual to use a path:-style
dependency. The ports should be named X and X-devel. The ports would install
the same files to the same places and would be marked as conflicting
On Oct 13, 2014, at 4:03 PM, Ryan Schmidt ryandes...@macports.org wrote:
All ports must install at least one file. You can look at other metaports to
see what they do. Typically they create a file called README and put either a
placeholder message or the port's description into it.
On Oct 18, 2014, at 9:35 PM, Mark Brethen wrote:
if {${name} eq ${subport}} {
supported_archs noarch
distfiles
archive_sites
use_configure no
build {}
depends_build-append\
port:reduce-common\
port:reduce-csl\
port:reduce-psl\
On Oct 18, 2014, at 9:59 PM, Mark Brethen wrote:
On Oct 18, 2014, at 9:50 PM, Ryan Schmidt wrote:
On Oct 18, 2014, at 9:35 PM, Mark Brethen wrote:
However an issue I've found is that if the install process is interrupted,
a subsequent re-issue of 'port install reduce' will fail due to
On Oct 18, 2014, at 10:59 PM, Mark Brethen mark.bret...@gmail.com wrote:
At this point I issued 'sudo port clean reduce-csl' and everything was ok,
but should portfiles anticipate such an event?
We generally consider interrupted builds to be user error. If we eventually
decide that we should
32 matches
Mail list logo
