Under "port upgrade --force", wouldn't it be better to wait until the Portfile
is ready to activate the newly built port before deactivating and uninstalling
the existing port?
$ sudo port -n upgrade --force phonon
---> Computing dependencies for phonon
---> Cleaning phonon
---> Unable to uni
On May 29, 2012, at 3:20 PM, Bjarne D Mathiesen wrote:
> +-+
> | |
> | !!! WORKING !!! |
> | |
> +-+
>
> # MacPorts path layout.
>
>prefix:/usr/local
>exec_prefix:${prefix}
>bindir:
On 2012-5-30 00:27 , Ryan Schmidt wrote:
>
> I'm not really clear on why we ever bother making new installers, since
> running the installer for any version of MacPorts automatically runs
> selfupdate, which will update the user to the current version of MacPorts. So
> any Tiger user can just r
On 2012-5-30 00:10 , Jeremy Lavergne wrote:
>> MacPorts 2.1.1 still works fine on Tiger and up.
>
> We're just no longer distributing installers for it? The site indicates
> Leopard is the only legacy platform with installers, implying Tiger can't
> install MacPorts.
It implies that you might h
On 2012-5-30 00:02 , Ryan Schmidt wrote:
> If a port doesn't support Tiger, it should so indicate with a pre-fetch error
> message. Examples of ports that do this include csu and nodejs.
Clearing the dependencies is also nice to do.
If you really want to keep the port available for Tiger, you c
Bjarne D Mathiesen wrote:
> Bjarne D Mathiesen wrote:
>> Layout of conf files :
>>
>> I'm somewhat enamored by the Ubuntu layout of the conf structure, where
>> they keep a conf-file for each module & have split the main httpd.conf
>> file into smaller parts.
>>
>> Would it be an idea for us to do
Bjarne D Mathiesen wrote:
> Bjarne D Mathiesen wrote:
>> Layout of conf files :
>>
>> I'm somewhat enamored by the Ubuntu layout of the conf structure, where
>> they keep a conf-file for each module & have split the main httpd.conf
>> file into smaller parts.
>>
>> Would it be an idea for us to do
Bjarne D Mathiesen wrote:
> Layout of conf files :
>
> I'm somewhat enamored by the Ubuntu layout of the conf structure, where
> they keep a conf-file for each module & have split the main httpd.conf
> file into smaller parts.
>
> Would it be an idea for us to do something similiar ???
> I'ld be
+-+
| |
| !!! WORKING !!! |
| |
+-+
# MacPorts path layout.
prefix:/usr/local
exec_prefix:${prefix}
bindir: ${exec_prefix}/bin
sbindir:${exec_prefix}/sbin
libdir:
On Tue, May 29, 2012 at 05:08:06PM -0500, Ryan Schmidt wrote:
> Forgot to actually commit this patchfile?
Yes, thank you for noticing, r93753.
--
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/
On May 29, 2012, at 16:52, c...@macports.org wrote:
> Revision: 93751
> https://trac.macports.org/changeset/93751
> Author: c...@macports.org
> Date: 2012-05-29 14:52:12 -0700 (Tue, 29 May 2012)
> Log Message:
> ---
> yubico-c-client: Fix build with automake 1.12
>
> Modif
On Tue, May 29, 2012 at 09:47:30PM +0200, Marin Saric wrote:
> 2) If not, give /Applications/Xcode.app a try, run xcode-select
> -switch and issue a warning.
Automagically modifying a user's setting is not a good idea. MacPorts
should at most warn and tell the user what to do.
Doesn't MacPorts al
Hi,
In an attempt to reproduce some build errors as accurately as
possible, I installed XCode and MacPorts on a bare bones machine with
only a fresh verison of 10.7 on it and a few unrelated apps. I then
installed the Command Line Tools, per the MacPorts user guide.
It turned out that I had to ma
> Thanks. I wish developers would fix bugs...
>
> https://bugzilla.gnome.org/show_bug.cgi?id=640834
Yeah, I know what you mean...
http://lists.macosforge.org/pipermail/macports-dev/2012-May/019098.html
http://lists.macosforge.org/pipermail/macports-dev/2012-May/019300.html
(fixed in this combo
> I saw that but I don't quite follow what it provides. Could you show sample
> output?
Ok, Ryan, what direction do you want the github portgroup to go in?
1) Have the portfile maintainer specify a git hash via git.branch (or
git.tag; whichever one it is)?
ex.
git.branch 9ccfac11f31d8d05d48092
>> Sure it is. You could just generate the files needed during the
>> post-destroot phase. Something like this:
>>
>> 1) loop through ${python.prefix}/{bin,etc,share,lib,libexec}
>> 2) output into 'select' files: base, none, etc.
>
> And which port is supposed to install these files?
>
> Multiple p
On May 29, 2012, at 09:49, Rainer Müller wrote:
> On 05/29/12 16:02, Ryan Schmidt wrote:
>> MacPorts 2.1.1 still works fine on Tiger and up.
>
> At least the selfupdate from 2.0.x to 2.1.x on Tiger is broken according
> to a report on StackOverflow [1].
>
> I never bothered to report it here as
On 29 mai 2012, at 16:49, Rainer Müller wrote:
> On 05/29/12 16:02, Ryan Schmidt wrote:
>> MacPorts 2.1.1 still works fine on Tiger and up.
>
> At least the selfupdate from 2.0.x to 2.1.x on Tiger is broken according
> to a report on StackOverflow [1].
If the problem is just related to an obsol
On 05/29/12 16:02, Ryan Schmidt wrote:
> MacPorts 2.1.1 still works fine on Tiger and up.
At least the selfupdate from 2.0.x to 2.1.x on Tiger is broken according
to a report on StackOverflow [1].
I never bothered to report it here as we previously considered versions
of Mac OS X below Leopard as
On May 29, 2012, at 09:15, Mojca Miklavec wrote:
> On Tue, May 29, 2012 at 4:02 PM, Ryan Schmidt wrote:
>> On May 29, 2012, at 08:50, Jeremy Lavergne wrote:
>>
What is the general strategy for handling such situations in MacPorts?
I guess that other developers might reject my patch if
On May 29, 2012, at 09:10, Jeremy Lavergne wrote:
>> Use of the current ports tree assumes use of the current version of
>> MacPorts. We don't support use of earlier versions of MacPorts.
>
> Well we've seen that not be the case when things from the future versions are
> sent out too early. Us
Jeremy Lavergne wrote:
>> MacPorts 2.1.1 still works fine on Tiger and up.
>
> We're just no longer distributing installers for it? The site indicates
> Leopard is the only legacy platform with installers, implying Tiger can't
> install MacPorts.
I'ld say that 10.5 Leopard is a safe bet.
10.5
On Tue, May 29, 2012 at 4:10 PM, Jeremy Lavergne wrote:
>
>> MacPorts 2.1.1 still works fine on Tiger and up.
>
> We're just no longer distributing installers for it? The site indicates
> Leopard is the only legacy platform with installers, implying Tiger can't
> install MacPorts.
There is no in
On Tue, May 29, 2012 at 4:02 PM, Ryan Schmidt wrote:
> On May 29, 2012, at 08:50, Jeremy Lavergne wrote:
>
>>> What is the general strategy for handling such situations in MacPorts?
>>> I guess that other developers might reject my patch if it drops
>>> support for 10.4, but with wxWidgets 2.9.4 on
> Use of the current ports tree assumes use of the current version of MacPorts.
> We don't support use of earlier versions of MacPorts.
Well we've seen that not be the case when things from the future versions are
sent out too early. Usually this is mitigated by wrapping with exists/info
checks
On May 29, 2012, at 08:50, Jeremy Lavergne wrote:
>> I was playing with wxWidgets 2.9 a bit. It builds fine without 10.6
>> (QuickDraw has been removed recently), so I guess that there should
>> not be any issues on Mountain Lion any more, but on the other hand I
>> noticed that those changes don'
> I was playing with wxWidgets 2.9 a bit. It builds fine without 10.6
> (QuickDraw has been removed recently), so I guess that there should
> not be any issues on Mountain Lion any more, but on the other hand I
> noticed that those changes don't support Tiger any more, so 2.9.4
> (whenever it's goi
Hello,
I was playing with wxWidgets 2.9 a bit. It builds fine without 10.6
(QuickDraw has been removed recently), so I guess that there should
not be any issues on Mountain Lion any more, but on the other hand I
noticed that those changes don't support Tiger any more, so 2.9.4
(whenever it's going
##
## config.layout -- Pre-defined Installation Path Layouts
##
## Hints:
## - layouts can be loaded with configure's --enable-layout=ID option
## - when no --enable-layout option is given, the default layout is
`Apache'
## - a trailing plus character (`+') on paths is replaced with a
##`/
On 2012-5-29 20:51 , Mojca Miklavec wrote:
> On Tue, May 29, 2012 at 12:24 PM, Joshua Root wrote:
>> On 2012-5-29 19:57 , Mojca Miklavec wrote:
>>> Hello,
>>>
>>> if I try to build wxWidgets with a patch that enables building with
>>> clang. But if I try to build +universal, it seems that I hit the
On Tue, May 29, 2012 at 12:24 PM, Joshua Root wrote:
> On 2012-5-29 19:57 , Mojca Miklavec wrote:
>> Hello,
>>
>> if I try to build wxWidgets with a patch that enables building with
>> clang. But if I try to build +universal, it seems that I hit the
>> problem of "looks like it's using parts of Qui
On 2012-5-29 19:57 , Mojca Miklavec wrote:
> Hello,
>
> if I try to build wxWidgets with a patch that enables building with
> clang. But if I try to build +universal, it seems that I hit the
> problem of "looks like it's using parts of QuickDraw that are gone in
> Lion", so I need to build with SD
On Tue, May 29, 2012 at 11:57 AM, Mojca Miklavec wrote:
> Hello,
>
> if I try to build wxWidgets with a patch that enables building with
> clang. But if I try to build +universal, it seems that I hit the
> problem of "looks like it's using parts of QuickDraw that are gone in
> Lion", so I need to b
Hello,
if I try to build wxWidgets with a patch that enables building with
clang. But if I try to build +universal, it seems that I hit the
problem of "looks like it's using parts of QuickDraw that are gone in
Lion", so I need to build with SDK for 10.6.
But then it fails with an equivalent of
34 matches
Mail list logo
