How to see just mtree violations?
Ryan Schmidt
ryandesign at macports.org
Mon Aug 27 23:50:30 PDT 2007
On Aug 27, 2007, at 22:39, Juan Manuel Palacios wrote:
> On Aug 20, 2007, at 7:41 AM, Vincent Lefevre wrote:
>
>> On 2007-08-20 03:36:38 -0500, Ryan Schmidt wrote:
>>
>>> We have the -t switch which we can turn on separately to activate
>>> trace mode, which is helpful for discovering undeclared
>>> dependencies. Is there a way that we could somehow see just the
>>> mtree violations, without all the other verbose/debug info?
>>
>> Couldn't a Portfile state that it doesn't violate mtree, so that
>> mtree violations are fatal in such cases?
>
> If I'm reading you correctly, you're proposing a Portfile only be
> accepted as clean if it specifically states it doesn't violate the
> mtree? If so, such functionality would require us going through
> every single one of our Portfiles and adapting them accordingly...
> which is needless to say a daunting task.
>
> To increase mtree violations visibility, at least for the time
> being, I propose promoting them to verbose output.
It turns out that if you just install the port normally, with neither
debug nor verbose output, mtree violations are already easily
visible. So no change to base is necessary.
More information about the macports-dev
mailing list