Re: Port deactivate boost hangs forever

2014-11-12 Thread Ryan Schmidt 

On Nov 12, 2014, at 5:15 PM, Clemens Lang wrote:

> On 10 Nov, 2014, at 12:34, Clemens Lang wrote:
> 
>> Just found https://github.com/couchbase/couchbase-lite-ios/issues/487, in 
>> specific
>> https://github.com/couchbase/couchbase-lite-ios/issues/487#issuecomment-58717637
>> which might explain our problems. We should check our indices.
> 
> Can somebody who can still reproduce the issue try again with
> https://trac.macports.org/changeset/128086? Unfortunately it seems boost 
> activation
> with and without this is currently fast (~ 90 sec) for me.
> 
> Maybe the performance only degrades if you still have older, inactive 
> versions of
> boost active? Could somebody who didn't delete the old boost version yet try
> re-activating the old version, then go back to the current one and measure 
> times
> both without and with the above update?


No change for me. Before or after r128086 MacPorts takes about 11 minutes 30 
seconds to activate or deactivate boost on Yosemite. I have only one version of 
boost installed:


$ port -v installed boost
The following ports are currently installed:
  boost @1.56.0_2+no_single+no_static+python27+universal (active) 
platform='darwin 14' archs='i386 x86_64'


$ sw_vers
ProductName:Mac OS X
ProductVersion: 10.10.1
BuildVersion:   14B23



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Port deactivate boost hangs forever

2014-11-12 Thread Clemens Lang 
Hi,

- On 10 Nov, 2014, at 12:34, Clemens Lang c...@macports.org wrote:

> Just found https://github.com/couchbase/couchbase-lite-ios/issues/487, in
> specific
> https://github.com/couchbase/couchbase-lite-ios/issues/487#issuecomment-58717637
> which might explain our problems. We should check our indices.

Can somebody who can still reproduce the issue try again with
https://trac.macports.org/changeset/128086? Unfortunately it seems boost 
activation
with and without this is currently fast (~ 90 sec) for me.

Maybe the performance only degrades if you still have older, inactive versions 
of
boost active? Could somebody who didn't delete the old boost version yet try
re-activating the old version, then go back to the current one and measure times
both without and with the above update?

-- 
Clemens Lang
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Fwd: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread Craig Treleaven 

At 3:58 AM +1100 11/13/14, Joshua Root wrote:

On 2014-11-13 03:53 , William Gallafent wrote:

 (Apologies, initially sent direct to Craig due to mailing list arguably
 being incorrectly configured Š)

 On 12 November 2014 15:44, Craig Treleaven mailto:ctrelea...@macports.org>> wrote:

 What's wrong with:


http://download-mirror.savannah.gnu.org/releases/linphone/3.7.x/sources/linphone-3.7.0.tar.gz


 The fact that it is not mentioned at
 http://www.linphone.org/technical-corner/linphone/downloads !


It's cleverly hidden among the binary downloads at
. :)


"Cleverly hidden"!  And I found it.  Boy, I'm 
going to be bragging about this all week!!  ;)


Craig

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Fwd: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread William Gallafent 
On 12 November 2014 16:58, Joshua Root  wrote:

>
> It's cleverly hidden among the binary downloads at
> . :)
>

:) Well spotted!

Anyway, I'm now working on building a portfile for belle-sip, since that
isn't currently present in MacPorts, and is a requirement for current
version of linphone. Don't worry, I found the download link for the sources
for that ;)

-- 
Bill Gallafent.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Fwd: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread Joshua Root 
On 2014-11-13 03:53 , William Gallafent wrote:
> (Apologies, initially sent direct to Craig due to mailing list arguably
> being incorrectly configured …)
> 
> On 12 November 2014 15:44, Craig Treleaven  > wrote:
> 
> What's wrong with:
> 
> 
> http://download-mirror.savannah.gnu.org/releases/linphone/3.7.x/sources/linphone-3.7.0.tar.gz
> 
> 
> The fact that it is not mentioned at
> http://www.linphone.org/technical-corner/linphone/downloads !

It's cleverly hidden among the binary downloads at
. :)

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: Recommendations for version numbers in port names

2014-11-12 Thread Joshua Root 
On 2014-11-12 17:14 , Lawrence Velázquez wrote:
> On Nov 10, 2014, at 3:02 PM, Bradley Giesbrecht  wrote:
> 
>> I don't know that I understand these variant checks, they seem to not 
>> produce the same result in all cases:
>>
>> http://trac.macports.org/browser/tags/release_2_3_2/base/src/port/port.tcl#L289
>> http://trac.macports.org/browser/tags/release_2_3_2/base/src/port/port.tcl#L1752
>> http://trac.macports.org/browser/tags/release_2_3_2/base/src/macports1.0/macports.tcl#L730
>> http://trac.macports.org/browser/tags/release_2_3_2/base/src/port1.0/portutil.tcl#L2289
>>
>> Would a proc for testing variant name sanity be worth the effort?
> 
> It would probably be a good idea to decide on an authoritative specification 
> and consolidate verification in a single place.

I think you mean validation? We don't actually do that anywhere at the
moment. All the places above are just parsing.

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Fwd: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread William Gallafent 
(Apologies, initially sent direct to Craig due to mailing list arguably
being incorrectly configured …)

On 12 November 2014 15:44, Craig Treleaven  wrote:

What's wrong with:
>
>
> http://download-mirror.savannah.gnu.org/releases/linphone/3.7.x/sources/linphone-3.7.0.tar.gz


The fact that it is not mentioned at
http://www.linphone.org/technical-corner/linphone/downloads !

-- 
Bill Gallafent.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Joshua Root 
On 2014-11-12 22:53 , Mihai Moldovan wrote:
> On 12.11.2014 11:09 am, Ryan Schmidt wrote:
>> The uncompressed idea.c file needs to be in the work directory. The 
>> compressed idea.c.gz file doesn't need to be copied there from the distpath.
> 
> The compressed file is automatically deleted by gunzip -d. Only idea.c will 
> remain.

You could do this:

system "< ${distpath}/idea.c.gz gunzip -dc > ${worksrcpath}/cipher/idea.c"

- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread Craig Treleaven 

At 3:35 PM + 11/12/14, William Gallafent wrote:
On 12 November 2014 15:26, Daniel J. Luke 
<dl...@geeklair.net> 
wrote:
 > On Nov 12, 2014, at 5:45 AM, William 
Gallafent 
<will...@gallaf.net> 
wrote:
 According to 
https://guide.macports.org/#reference.phases.fetch.git 
I am able to set the url and tag to fetch Š but 
for a particular port I'm playing with I also 
need to add the "--recursive" option in order 
to get the submodules in place. Alternatively, 
I would need to run "git submodule update 
--init --recursive" immediately after the fetch.


 Any thoughts or advice?


First, be sure you actually need to use git to 
fetch the source (it's /much/ better to pull a 
tarball than to pull source from 
git/mercurial/svn/cvs/whatever).


Fair point! The only links given to source for 
this project are to git repositories, 
unfortunately - 
http://www.linphone.org/technical-corner/linphone/downloads 
Š if there's a location from which I may 
download source tarballs, then so much the 
better, but I haven't found one yet!


What's wrong with:

http://download-mirror.savannah.gnu.org/releases/linphone/3.7.x/sources/linphone-3.7.0.tar.gz

Craig
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread William Gallafent 
On 12 November 2014 15:26, Daniel J. Luke  wrote:

> > On Nov 12, 2014, at 5:45 AM, William Gallafent 
> wrote:
> > According to https://guide.macports.org/#reference.phases.fetch.git I
> am able to set the url and tag to fetch … but for a particular port I'm
> playing with I also need to add the “--recursive” option in order to get
> the submodules in place. Alternatively, I would need to run “git submodule
> update --init --recursive” immediately after the fetch.
> >
> > Any thoughts or advice?
>
> First, be sure you actually need to use git to fetch the source (it's
> /much/ better to pull a tarball than to pull source from
> git/mercurial/svn/cvs/whatever).
>

Fair point! The only links given to source for this project are to git
repositories, unfortunately -
http://www.linphone.org/technical-corner/linphone/downloads … if there's a
location from which I may download source tarballs, then so much the
better, but I haven't found one yet!

There's a ticket open to update the linphone port already, incidentally,
but I decided not to hold my breath (that ticket has been open for 16
months …), and to update the port myself.

I'm not sure if there's a hook for you to pass in additional git args, but
> even if there isn't - it should be relatively trivial for youu to add a
> 'post-fetch' phase to do whatever you want to have happen right after the
> fetch.

[snip explanation]

That looks rather like just the ticket. Thanks for the pointers!

-- 
Bill Gallafent.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread Daniel J. Luke 
> On Nov 12, 2014, at 5:45 AM, William Gallafent  wrote:
> According to https://guide.macports.org/#reference.phases.fetch.git I am able 
> to set the url and tag to fetch … but for a particular port I'm playing with 
> I also need to add the “--recursive” option in order to get the submodules in 
> place. Alternatively, I would need to run “git submodule update --init 
> --recursive” immediately after the fetch.
> 
> Any thoughts or advice?

First, be sure you actually need to use git to fetch the source (it's /much/ 
better to pull a tarball than to pull source from 
git/mercurial/svn/cvs/whatever).

I'm not sure if there's a hook for you to pass in additional git args, but even 
if there isn't - it should be relatively trivial for youu to add a 'post-fetch' 
phase to do whatever you want to have happen right after the fetch.

Note that the github portgroup says this:

# Some projects' tag- or commit-based distfiles will not contain all the
# necessary files, if the project uses git submodules. If available, use a
# distfile from "releases" or "downloads" instead, as described above. If the
# project does not provide those, encourage the project's developers to provide
# releases. Until they do, fetch from git instead of from a distfile, and add a
# post-fetch block to fetch the submodules:
#
#   fetch.type  git
#
#   post-fetch {
#   system -W ${worksrcpath} "git submodule update --init"
#   }

--
Daniel J. Luke  
 
++  
  
| * dl...@geeklair.net * |  

| *-- http://www.geeklair.net -* |  

++  
  
|   Opinions expressed are mine and do not necessarily   |  

|  reflect the opinions of my employer.  |  

++




___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Mihai Moldovan 
On 12.11.2014 12:53 pm, Mihai Moldovan wrote:
> On 12.11.2014 11:32 am, Ryan Schmidt wrote:
>> Also, why not put the post-extract variant into the variant to
>> which it belongs?
>
> Yes, good idea, will do.

r128058.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Mihai Moldovan 
On 12.11.2014 11:09 am, Ryan Schmidt wrote:
> The uncompressed idea.c file needs to be in the work directory. The 
> compressed idea.c.gz file doesn't need to be copied there from the distpath.

The compressed file is automatically deleted by gunzip -d. Only idea.c will 
remain.


On 12.11.2014 11:32 am, Ryan Schmidt wrote:
> Also, why not put the post-extract variant into the variant to which it 
> belongs?

Yes, good idea, will do.



Mihai
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

How to specify commandline options to git for the fetch phase of a port?

2014-11-12 Thread William Gallafent 
Hi all,

According to https://guide.macports.org/#reference.phases.fetch.git I am
able to set the url and tag to fetch … but for a particular port I'm
playing with I also need to add the “--recursive” option in order to get
the submodules in place. Alternatively, I would need to run “git submodule
update --init --recursive” immediately after the fetch.

Any thoughts or advice?

Thanks,

-- 
Bill Gallafent.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Ryan Schmidt 

On Nov 12, 2014, at 4:09 AM, Ryan Schmidt wrote:
> 
> On Nov 12, 2014, at 4:08 AM, Mihai Moldovan wrote:
> 
>> On 12.11.2014 09:02 am, Ryan Schmidt wrote:
>>> 
>>> There's no real need to copy the idea.c.gz distfile into the work 
>>> directory, is there? You could decompress from its location in distpath.
>> 
>> The uncompressed idea.c is a source file used while building (or so it was
>> intended, I didn't take a close look if it's actually used yet.)
>> 
>> By any means, it has to be copied to the work dir at some point anyway, 
>> unless I
>> misunderstand your question?
> 
> The uncompressed idea.c file needs to be in the work directory. The 
> compressed idea.c.gz file doesn't need to be copied there from the distpath.
> 

Also, why not put the post-extract variant into the variant to which it belongs?



Index: Portfile
===
--- Portfile(revision 128055)
+++ Portfile(working copy)
@@ -61,13 +61,10 @@
   sha1   82fded4ec31b97b3b2dd22741880b67cfee40f84 \
   rmd160 e35be5a031d10d52341ac5f029d28f811edd908d
 extract.only${distname}${extract.suffix}
-}
 
-post-extract {
-if {[variant_isset idea]} {
-copy ${distpath}/idea.c.gz ${worksrcpath}/cipher
+post-extract {
 move ${worksrcpath}/cipher/idea.c ${worksrcpath}/cipher/idea.c.orig
-system -W "${worksrcpath}/cipher" "gunzip -d idea.c.gz"
+system "gzcat < ${distpath}/idea.c.gz > ${worksrcpath}/cipher/idea.c"
 }
 }
 



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Ryan Schmidt 

On Nov 12, 2014, at 4:08 AM, Mihai Moldovan wrote:

> On 12.11.2014 09:02 am, Ryan Schmidt wrote:
>> 
>> There's no real need to copy the idea.c.gz distfile into the work directory, 
>> is there? You could decompress from its location in distpath.
> 
> The uncompressed idea.c is a source file used while building (or so it was
> intended, I didn't take a close look if it's actually used yet.)
> 
> By any means, it has to be copied to the work dir at some point anyway, 
> unless I
> misunderstand your question?

The uncompressed idea.c file needs to be in the work directory. The compressed 
idea.c.gz file doesn't need to be copied there from the distpath.


___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Mihai Moldovan 
On 12.11.2014 09:02 am, Ryan Schmidt wrote:
> 
> There's no real need to copy the idea.c.gz distfile into the work directory, 
> is there? You could decompress from its location in distpath.

The uncompressed idea.c is a source file used while building (or so it was
intended, I didn't take a close look if it's actually used yet.)

By any means, it has to be copied to the work dir at some point anyway, unless I
misunderstand your question?


Mihai
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [128051] trunk/dports/mail/gnupg/Portfile

2014-11-12 Thread Ryan Schmidt 

> On Nov 11, 2014, at 8:40 PM, io...@macports.org wrote:
> 
> Revision
> 128051
> Author
> io...@macports.org
> Date
> 2014-11-11 18:40:12 -0800 (Tue, 11 Nov 2014)
> Log Message
> 
> gnupg: do not abuse patchfiles to download and uncompress an extra source 
> file. no rev-bump on purpose.
> Modified Paths
> 
>   • trunk/dports/mail/gnupg/Portfile
> Diff
> 
> Modified: trunk/dports/mail/gnupg/Portfile (128050 => 128051)

> +post-extract {
> +if {[variant_isset idea]} {
> +copy ${distpath}/idea.c.gz ${worksrcpath}/cipher
> +move ${worksrcpath}/cipher/idea.c ${worksrcpath}/cipher/idea.c.orig
> +system -W "${worksrcpath}/cipher" "gunzip -d idea.c.gz"
> +}
> +}

There's no real need to copy the idea.c.gz distfile into the work directory, is 
there? You could decompress from its location in distpath.



___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev