On Wed, 2004-10-06 at 14:39, John Dennis wrote: > Is this Makefile cruft or should this be executed? Note that > mailman-2.1.5/Makefile.in removes the "other" read permission on > $prefix/archives/private, but it leaves group read/write. This suggests > to me that $prefix/cgi-bin/private with setgid and arbitrary owner (e.g. > without running the "finish") is fine and thus leads me to the > conclusion the finish target is cruft. > > Is this right?
Yes. I don't remember why "make finish" was added, but it's probably cruft left over from when it was possible to run MM2 from the source directory. I briefly skimmed the CVS logs, but they didn't provide much of a clue. All the 'finish' targets can probably be ignored or removed. -Barry
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers Unsubscribe: http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org
