[Mailman-Developers] make finish?

Barry Warsaw barry at python.org
Wed Oct 6 21:42:05 CEST 2004

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.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 307 bytes
Desc: This is a digitally signed message part
Url : http://mail.python.org/pipermail/mailman-developers/attachments/20041006/80d64df4/attachment.pgp

More information about the Mailman-Developers mailing list