Le 15 août 07 à 22:14, Juan Manuel Palacios a écrit :
Good evening everyone!
MacPorts 1.5.2 is now available through selfupdate to temporarily
downgrade from fatal errors to warnings all the mtree violations
some ports are showing. Users should upgrade to this new release
but
On Aug 15, 2007, at 18:51, [EMAIL PROTECTED] wrote:
Ryan Schmidt writes:
By the way, it should be noted in the new guide that export
tarballs
are preferred over checkout ones.
I don't need all of those .svn and CVS, I just want the sources.
You mean to state that it is preferred that port
N_Ox wrote:
For this port to be really useful, every port depending on port:php5
should depend on (path|lib):*:php5.
Can't you do the usual workaround, and installing the php5 port
deactivated to fill dependencies and then install the php5-devel port
activated to get the new version ?
Le 16 août 07 à 10:56, Anders F Björklund a écrit :
N_Ox wrote:
For this port to be really useful, every port depending on
port:php5 should depend on (path|lib):*:php5.
Can't you do the usual workaround, and installing the php5 port
deactivated to fill dependencies and then install the
N_Ox wrote:
Le 14 août 07 à 19:58, N_Ox a écrit :
Le 12 août 07 à 05:28, N_Ox a écrit :
From what I've understood, the problem with default variants is that
if we do something like `port foo -bar` and that foo has
`default_variants +bar`, if an upgrade of foo is released, then `port
Le 16 août 07 à 15:12, Anders F Björklund a écrit :
N_Ox wrote:
I'm curious what is the logic for having two separate directories
one named libexec and the other named bin?
From porthier(7):
libexec/ system daemons system utilities
(executed by
Le 07-08-16 à 09:37, N_Ox a écrit :
Le 16 août 07 à 15:19, Yves de Champlain a écrit :
Le 07-08-16 à 08:49, N_Ox a écrit :
Le 16 août 07 à 13:47, Rainer Müller a écrit :
N_Ox wrote:
Le 14 août 07 à 19:58, N_Ox a écrit :
Le 12 août 07 à 05:28, N_Ox a écrit :
From what I've
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Blair Zajac wrote:
Anders F Björklund wrote:
For MacPorts 1.6, it might be a good idea to consider moving
macports1.0 from the current @TCL_PACKAGE_DIR@ directory to the
@prefix_expanded@/share/macports/Tcl directory, in order to make the
On Aug 16, 2007, at 10:55, Blair Zajac wrote:
Landon Fuller wrote:
On Aug 16, 2007, at 02:15, Anders F Björklund wrote:
For MacPorts 1.6, it might be a good idea to consider moving
macports1.0 from the current @TCL_PACKAGE_DIR@ directory to the
@prefix_expanded@/share/macports/Tcl
On Aug 16, 2007, at 11:10, Blair Zajac wrote:
Landon Fuller wrote:
On Aug 16, 2007, at 10:55, Blair Zajac wrote:
Landon Fuller wrote:
On Aug 16, 2007, at 02:15, Anders F Björklund wrote:
For MacPorts 1.6, it might be a good idea to consider moving
macports1.0 from the current
On Aug 16, 2007, at 12:10, Blair Zajac wrote:
I'm just trying to get a sense of what we're talking about here,
as we're discussing trade offs between competing concerns.
OK, then I'll simplify.
Arguments For Moving:
Developers can install multiple versions without passing --
Landon Fuller wrote:
On Aug 16, 2007, at 11:10, Blair Zajac wrote:
Landon Fuller wrote:
On Aug 16, 2007, at 10:55, Blair Zajac wrote:
Landon Fuller wrote:
On Aug 16, 2007, at 02:15, Anders F Björklund wrote:
For MacPorts 1.6, it might be a good idea to consider moving
macports1.0 from
Landon Fuller wrote:
The choice was originally made to support the GUI PortsManager app. I
think it was a good choice.
I keeping the default of /Library/Tcl/macports1.0 is enough bring the
GUI PortsManager.app back to life in good working order, then by all
means keep the current location
svn: PROPFIND request failed on '/repository/macports/trunk'
svn: PROPFIND of '/repository/macports/trunk': Could not resolve hostname
`svn.macports.org': No address associated with nodename
(http://svn.macports.org)
Updating the dports tree from
14 matches
Mail list logo
