On 2015-9-29 11:50 , Craig Treleaven wrote:
> Hi:
>
> What order does MacPorts use for fetching dist files? My impression was that
> MacPorts would try to:
>
> 1) use a ‘close by’ mirror (based on ping times)
> 2) fetch from the main MacPorts dist file server
>
On 2015-9-29 01:33 , Tiago Freitas Pereira wrote:
> Hi,
>
> I'm developing a port using the portgroup python (called py-bob).
>
> Executing some tests locally, I can install successfully the port using
> the commands
> {{{
> sudo port install py27-bob #for python 2.7
> }}}
> or
> {{{
> sudo
Hi,
I'm developing a port using the portgroup python (called py-bob).
Executing some tests locally, I can install successfully the port using the
commands
{{{
sudo port install py27-bob #for python 2.7
}}}
or
{{{
sudo port install py34-bob #for python 3.4
}}}
However, if I do
{{{
sudo port
The issue exists in more general form for cases like ffmpeg and ffmpeg-devel
when the dylib id changes (eg: when bumping it due to binary incompatibility).
If the user goes and installs ffmpeg-devel, then anything that depends on
ffmpeg needs to be built from source because the buildbot
Hi,
I'd like to bring up something related to alternative ports and the build bots.
It concerns my qt5-kde port (submitted on trac), but the principle is more
generic.
In short, consider 2 ports that are supposed to be alternatives like port:foo
and port:foo-devel, but that are different
Hi:
What order does MacPorts use for fetching dist files? My impression was that
MacPorts would try to:
1) use a ‘close by’ mirror (based on ping times)
2) fetch from the main MacPorts dist file server
(http://distfiles.macports.org/)
3) fall back to the master_site (GitHub, in my case[a])
> On Sep 28, 2015, at 5:58 PM, take...@macports.org wrote:
>
> Revision
> 140646
> Author
> take...@macports.org
> Date
> 2015-09-28 15:58:38 -0700 (Mon, 28 Sep 2015)
> Log Message
>
> ppc-linux-binutils: update to 2.25
> Modified: trunk/dports/cross/ppc-linux-binutils/Portfile (140645 =>
