On 2015-4-26 06:30 , petr wrote:
>
> Hi all,
>
> I am wondering if there is a simple way to avoid fetching distfiles from the
> macports mirrors. I would need to do this mainly for testing, or things like
> to detect stealth updates or broken master_sites.
FYI, there's 'port distcheck' for doi
On Apr 25, 2015, at 3:30 PM, petr wrote:
> I am wondering if there is a simple way to avoid fetching distfiles from the
> macports mirrors. I would need to do this mainly for testing, or things like
> to detect stealth updates or broken master_sites.
You can exclude servers by listing their ho
Hi all,
I am wondering if there is a simple way to avoid fetching distfiles from the
macports mirrors. I would need to do this mainly for testing, or things like to
detect stealth updates or broken master_sites.
Thanks!
~petr
___
macports-dev mailing
No progress on current build 28518 for over 12 hours. Attempts to stop
and restart via web interface ineffective.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 25 Apr 2015, at 17:49, Lawrence Velázquez wrote:
> On Apr 25, 2015, at 5:49 AM, petr <9...@ingv.it> wrote:
>
>> To my understanding the +clang3{0,1,2} refer to clang-3.{0,1,2} respectively.
>
> Yup.
>
>> These clang ports are no obsolete.
>
> Yup.
>
>> However, there are still quite some
On Apr 25, 2015, at 5:49 AM, petr <9...@ingv.it> wrote:
> To my understanding the +clang3{0,1,2} refer to clang-3.{0,1,2} respectively.
Yup.
> These clang ports are no obsolete.
Yup.
> However, there are still quite some ports around with these variants, so I
> guess these clang3{0,1,2} varia
Hi all,
To my understanding the +clang3{0,1,2} refer to clang-3.{0,1,2} respectively.
These clang ports are no obsolete.
However, there are still quite some ports around with these variants, so I
guess these clang3{0,1,2} variants (and maybe others) should be removed?
~petr
_
