On Dec 11, 2014, at 1:46 PM, Clemens Lang wrote:
> Hi,
>
> - On 11 Dec, 2014, at 22:31, Bradley Giesbrecht pixi...@macports.org
> wrote:
>
>> If installation/activation of ports via dependency ignores installed inactive
>> versions I think this a bug in base.
>>
>> Shouldn't dependency i
Hi,
- On 11 Dec, 2014, at 22:31, Bradley Giesbrecht pixi...@macports.org wrote:
> If installation/activation of ports via dependency ignores installed inactive
> versions I think this a bug in base.
>
> Shouldn't dependency installation take into consideration multiple inactive
> versions as
> On Dec 11, 2014, at 3:58 PM, René J.V. Bertin wrote:
>
> On Thursday December 11 2014 15:32:03 Lawrence Velázquez wrote:
>
> > Using DESTDIR is a pretty common convention for Unix-y build systems. Is
> > INSTALL_ROOT the convention somewhere else?
>
> I think it's what qmake produces, so it
On Dec 11, 2014, at 1:06 PM, Bradley Giesbrecht wrote:
>
> On Dec 11, 2014, at 12:41 PM, Joshua Root wrote:
>
>> On 2014-12-12 06:51 , Bradley Giesbrecht wrote:
>>>
>>> On Dec 10, 2014, at 12:19 AM, Ryan Schmidt wrote:
>>>
On Dec 9, 2014, at 1:21 PM, Bradley Giesbrecht wrote:
>>>
On Dec 11, 2014, at 12:41 PM, Joshua Root wrote:
> On 2014-12-12 06:51 , Bradley Giesbrecht wrote:
>>
>> On Dec 10, 2014, at 12:19 AM, Ryan Schmidt wrote:
>>
>>>
>>> On Dec 9, 2014, at 1:21 PM, Bradley Giesbrecht wrote:
>>>
Is this behavior by design?
$ sudo port -q deactiva
On 2014-12-12 06:51 , Bradley Giesbrecht wrote:
>
> On Dec 10, 2014, at 12:19 AM, Ryan Schmidt wrote:
>
>>
>> On Dec 9, 2014, at 1:21 PM, Bradley Giesbrecht wrote:
>>
>>> Is this behavior by design?
>>>
>>> $ sudo port -q deactivate sqlgrey postfix
>>> ---> Deactivating sqlgrey @1.8.0-rc2_2+mys
On Dec 10, 2014, at 7:20 AM, Jeremy Lavergne wrote:
> On Dec 10, 2014, at 3:19 AM, Ryan Schmidt wrote:
>
>> It looks expected, in so far as you have multiple versions of postfix
>> installed, asked MacPorts to activate postfix, and did not specify which one
>> you wanted to activate.
>
> The
On Dec 10, 2014, at 12:19 AM, Ryan Schmidt wrote:
>
> On Dec 9, 2014, at 1:21 PM, Bradley Giesbrecht wrote:
>
>> Is this behavior by design?
>>
>> $ sudo port -q deactivate sqlgrey postfix
>> ---> Deactivating sqlgrey @1.8.0-rc2_2+mysql+perl5_20
>> ---> Deactivating postfix @2.11.3_0
>> $ s
On 2014-12-11 19:48 , Joshua Root wrote:
> On 2014-12-11 19:03 , Marko wrote:
>> Hi Josh,
>>
>> On 11 Dec 2014, at 08:56 , Joshua Root wrote:
>>> It's perfectly safe, it just doesn't give users who installed it under
>>> the old name an automated update path. (I assume you would edit the
>>> portf
On 2014-12-11 19:40 , Marko Käning wrote:
> Hi Josh,
>
> on a clean VM I see after selfupdate, that the port kcm-baloo-advanced has
> been registered correctly,
> but of course under the different port dir:
> ---
> $ port dir kcm-baloo-advanced
> /opt/local/var/macports/sources/rsync.macports.or
On 2014-12-11 19:03 , Marko wrote:
> Hi Josh,
>
> On 11 Dec 2014, at 08:56 , Joshua Root wrote:
>> It's perfectly safe, it just doesn't give users who installed it under
>> the old name an automated update path. (I assume you would edit the
>> portfile to change the name between the move and the
Hi Josh,
on a clean VM I see after selfupdate, that the port kcm-baloo-advanced has been
registered correctly,
but of course under the different port dir:
---
$ port dir kcm-baloo-advanced
/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/ports/kde/baloo-kcm-advanced
---
So, t
Hi Josh,
On 11 Dec 2014, at 08:56 , Joshua Root wrote:
> It's perfectly safe, it just doesn't give users who installed it under
> the old name an automated update path. (I assume you would edit the
> portfile to change the name between the move and the commit.)
the Portfile contains the required
13 matches
Mail list logo