Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Bradley Giesbrecht
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

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Clemens Lang
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

Re: how do ports install into ${destroot} instead of into ${prefix} directly?

2014-12-11 Thread Daniel J. Luke
> 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

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Bradley Giesbrecht
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: >>>

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Bradley Giesbrecht
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

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Joshua Root
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

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Ryan Schmidt
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

Re: port activate ignores multiple installed versions and variants of inactive dependents

2014-12-11 Thread Bradley Giesbrecht
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

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-11 Thread Joshua Root
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

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-11 Thread Joshua Root
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

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-11 Thread Joshua Root
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

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-11 Thread Marko Käning
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

Re: How to recover from wrong port naming at time of 1st commit?

2014-12-11 Thread Marko Käning
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