I've added some configure. flags for +universal variants,
and also to the macports.conf file for providing defaults.
They are:
- universal_target
# for setting macosx_deployment_target and configure target
Default: 10.4
- universal_sysroot
# the SDK sysroot to use, normally for the
Some of our non-devel ports do install development versions because
the latest releases don't work at all or are years out of date, say.
But generally this should not be the case. If you think the latest
stable release of a program is not suitable, then you should push
the developers to
On Feb 7, 2008, at 9:03 AM, Emmanuel Hainry wrote:
Seeing that there are 5 different postgresql port (7,
80, 81, 82, 83) makes me quite puzzled, which one is considered
stable?
Each postgres version in macports has an on-disk format that is
incompatible with the next (newer) release.
On 2008-02-07 15:21:41 +0100, Thomas de Grivel wrote:
2008/2/7, Ryan Schmidt [EMAIL PROTECTED]:
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is newer than the latest
development version. If we act on this proposal, then -latest
On Feb 7, 2008, at 09:10, Vincent Lefevre wrote:
On 2008-02-07 15:21:41 +0100, Thomas de Grivel wrote:
2008/2/7, Ryan Schmidt:
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is newer than the
latest
development version. If
On 2008-02-07 09:47:45 -0500, Daniel J. Luke wrote:
On Feb 7, 2008, at 9:03 AM, Emmanuel Hainry wrote:
Seeing that there are 5 different postgresql port (7,
80, 81, 82, 83) makes me quite puzzled, which one is considered
stable?
Each postgres version in macports has an on-disk format that
2008/2/7, js [EMAIL PROTECTED]:
If the developer call it as stable and the other's development,
Let' follow it.
Anyone who like to use newer can easily choose -devel one.
I think we all agree on this (we dont have time to test stability, ffs).
2008/2/7, Ryan Schmidt [EMAIL PROTECTED]:
It was
On 2008-02-07 22:08:57 +0900, js wrote:
I agree with you,
but I think that the situation that devel-ver stable-ver is very
rare. I've never seen it. (By newer, you means the version number is
greater, right?)
It happens for tin almost each time a new stable version is released
(because it is
On 2008-02-07 23:00:14 +0900, js wrote:
If the developer call it as stable and the other's development,
Let' follow it.
Anyone who like to use newer can easily choose -devel one.
However this may be confusing for the end user, as depending on the
developers, unstable doesn't always mean the
Citando js :
On Feb 7, 2008 1:58 PM, Ryan Schmidt [EMAIL PROTECTED] wrote:
I think -devel is better.
For one thing, it's more intuitive.
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is newer than the latest
If the developer call it as stable and the other's development,
Let' follow it.
Anyone who like to use newer can easily choose -devel one.
On Feb 7, 2008 10:50 PM, Vincent Lefevre [EMAIL PROTECTED] wrote:
On 2008-02-07 22:08:57 +0900, js wrote:
I agree with you,
but I think that the
On Feb 7, 2008, at 03:30, Anders F Björklund wrote:
I've added some configure. flags for +universal variants,
and also to the macports.conf file for providing defaults.
They are:
- universal_target
# for setting macosx_deployment_target and configure target
Default: 10.4
-
Sorry, emergency maintenance. Its all back now, let me know if you
still have trouble. The short notice was due to the general slowness
you mentioned. I'll be doing some more stuff over the next few days
too to try and help.
-Bill
On Feb 7, 2008, at 6:20 PM, Ryan Schmidt wrote:
Trac has
Trac has been very slow lately, but right now it's not responding at
all:
The operation timed out when attempting to contact trac.macosforge.org.
The requested site did not respond to a connection request and Camino
has stopped waiting for a reply.
and neither is Subversion:
gnucash $ svn
Super, thanks! It seems to be back up for now.
On Feb 7, 2008, at 20:44, William Siegrist wrote:
Sorry, emergency maintenance. Its all back now, let me know if you
still have trouble. The short notice was due to the general
slowness you mentioned. I'll be doing some more stuff over the
On Feb 7, 2008, at 21:34, [EMAIL PROTECTED] wrote:
Revision: 33938
http://trac.macosforge.org/projects/macports/changeset/33938
Author: [EMAIL PROTECTED]
Date: 2008-02-07 19:34:55 -0800 (Thu, 07 Feb 2008)
Log Message:
---
macports1.0/macports.tcl:
Add --prepend option
Ryan Schmidt wrote:
What is being prepended to what? Or did you mean pretend?
Ouch. Of course I meant that! Somehow I got it wrong and didn't notice
it at all. Sorry...
Thanks, I am going to fix this.
Rainer
___
macports-dev mailing list
2008/2/7, Ryan Schmidt [EMAIL PROTECTED]:
On Feb 7, 2008, at 09:10, Vincent Lefevre wrote:
On 2008-02-07 15:21:41 +0100, Thomas de Grivel wrote:
2008/2/7, Ryan Schmidt:
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is
18 matches
Mail list logo
