On 2015-10-04 03:40, Bradley Giesbrecht wrote:
> Is there a macports mechanism for declaring a port cannot be a dependent?
I don't think this happens often enough that we need a technical
solution to prevent it. At least I cannot think of any other port.
Rainer
On Oct 3, 2015, at 8:40 PM, Bradley Giesbrecht wrote:
> Is there a macports mechanism for declaring a port cannot be a dependent?
I don't think so.
___
macports-dev mailing list
macports-dev@lists.macosforge.org
- On 4 Oct, 2015, at 03:40, Bradley Giesbrecht pixi...@macports.org wrote:
> My concern is that since there is consensus that we should not report without
> user intention that a mistake like mine where I did not know mpstat used
> startupitem.autoload that one cannot easily fix the issue
> On Oct 3, 2015, at 1:21 PM, Clemens Lang wrote:
>
>
>
> - On 3 Oct, 2015, at 22:14, Clemens Lang c...@macports.org wrote:
>
>> I don't think forcing users to participate in statistics collection like
>> this is OK with their consent, at least not according to German
Hi,
- On 3 Oct, 2015, at 22:03, pixi...@macports.org wrote:
> [140813] trunk/dports/science/OpenCoarrays/Portfile
> Revision 140813
> Author pixi...@macports.org
> Date 2015-10-03 13:03:03 -0700 (Sat, 03 Oct 2015)
> Log Message Add dependency on mpstats.
- On 3 Oct, 2015, at 22:14, Clemens Lang c...@macports.org wrote:
> I don't think forcing users to participate in statistics collection like
> this is OK with their consent, at least not according to German data
I obviously meant withOUT their explicit consent, sorry for
- On 3 Oct, 2015, at 23:33, Bradley Giesbrecht pixi...@macports.org wrote:
> I understood that even with mpstatl installed it was still opt-in and the user
> had to make a config change to actually report. Is my understanding incorrect?
mpstats uses startupitem.autoload to automatically
> On Oct 3, 2015, at 2:44 PM, Clemens Lang wrote:
>
>
>
> - On 3 Oct, 2015, at 23:33, Bradley Giesbrecht pixi...@macports.org wrote:
>
>> I understood that even with mpstatl installed it was still opt-in and the
>> user
>> had to make a config change to actually