On Aug 12, 2007, at 15:08, Weissmann Markus wrote:
Just before this one gets a stopper for a lot of ports:
Juan will look into doing a 1.5.2 (or whatever) release which
includes the fix for the "/Applications" bug and also turns the
violation errors into non-fatal warnings (for now). I shou
On 12 Aug 2007, at 22:14, Weissmann Markus wrote:
On 12 Aug 2007, at 07:25, [EMAIL PROTECTED] wrote:
Ryan Schmidt <[EMAIL PROTECTED]> writes:
I'm not sure I like that mtree violations are fatal errors. The
ports
that are now failing to install because of mtree violations
installed
just fi
On 12 Aug 2007, at 22:36, Anders F Björklund wrote:
Weissmann Markus wrote:
we've documented the should-be state of the layout of the ports-
filesystems years ago already - see porthier(7); if ports fail
because of this right now, it is most likely either because our
implementation is faul
Weissmann Markus wrote:
we've documented the should-be state of the layout of the
ports-filesystems years ago already - see porthier(7); if ports fail
because of this right now, it is most likely either because our
implementation is faulty or the port is buggy.
Seems like "src" is missing fr
On 12 Aug 2007, at 07:25, [EMAIL PROTECTED] wrote:
Ryan Schmidt <[EMAIL PROTECTED]> writes:
I'm not sure I like that mtree violations are fatal errors. The ports
that are now failing to install because of mtree violations installed
just fine in MacPorts 1.5.0. Why should they now fail to instal
Sun, 12 Aug 2007 (00:02 -0500 UTC) Ryan Schmidt wrote:
I'm not sure I like that mtree violations are fatal errors. The ports that
are now failing to install because of mtree violations installed just fine in
MacPorts 1.5.0. Why should they now fail to install? Their content has not
changed. Su
Ryan Schmidt <[EMAIL PROTECTED]> writes:
>I'm not sure I like that mtree violations are fatal errors. The ports
>that are now failing to install because of mtree violations installed
>just fine in MacPorts 1.5.0. Why should they now fail to install?
>Their content has not changed. Sure, they
I'm not sure I like that mtree violations are fatal errors. The ports
that are now failing to install because of mtree violations installed
just fine in MacPorts 1.5.0. Why should they now fail to install?
Their content has not changed. Sure, they may be installing things in
places they sho
