On Saturday 02 October 2004 20:31 CET Justin Mason wrote:
> [EMAIL PROTECTED] writes:
> > Author: mss
> > Date: Sat Oct  2 08:29:31 2004
> > New Revision: 51805
> >
> > Modified:
> >    spamassassin/trunk/Makefile.PL
> > Log:
> > Just for fun...
>
> what does this do?   could we get some more descriptive commit messages,
> and possibly some discussion before the top-level Makefile.PL is changed
> like this?

Have a look at the EU::MM manpage, it's tirival as nothing.  EU::MM per 
default offers a 'ci' target which does a checkin.  Unfortunately does it 
default to rcs so when I accidently typed 'make ci' instead of 'svn ci' 
some weird stuff happened.  So I added those two lines to make 'make ci' 
call 'svn ci'.  Not very useful but doesn't hurt either  *shrugs*

> also, how does "make manifest" "update the manifest"?  The whole idea
> of that file is that it is *manually* maintained, not automatically,
> to avoid accidental inclusion of built files.

The file can be updated either manually or automatically via 'make 
manifest'.  The latter is much easier, as long as you have a good 
MANIFEST.SKIP file (I updated ours accordingly).  So in 90% of all cases 
when you added, moved, or removed a file you now just type 'make manifest' 
instead of keeping that stupid file up-to-date manually.  It's even nice 
enough to tell you 'Added file foo', 'Removed file bar', and so on, so you 
can check if everything's correct.  Try it, it's really nice.

If we don't use that automatism, we should remove the file MANIFEST.SKIP 
completely as keeping two of them up-to-date is completely useless.

Cheers,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Reply via email to