[Distutils] generate MANIFEST from CVS

[Bernhard Herzog]

Rene Liebscher <R.Liebscher@gmx.de> writes:

> Bernhard Herzog wrote:
> > 
> > The cvs command could do this, too: if run in a directory checked out
> > from CVS, i.e. if CVS/Entries exists, generate the list of
> > CVS-controlled files, write them into MANIFEST.cvs and include them in
> > MANIFEST. If not run in a CVS directory, MANIFEST.cvs must exist and the
> > files listed there are included in MANIFEST. In both cases MANIFEST.cvs
> > will have to be in MANIFEST, too.
> > 
> > Thoughts?
> > 
> >    Bernhard
> > 
> It is not necessary to add such a MANIFEST.cvs file. If you are start
> creating a file which contains filenames, you could also write a
> complete
> MANIFEST file. (So you don't need a MANIFEST.in file.) 

Well, the reason I think it might be useful to have the MANIFEST.cvs in
addition to the MANIFEST.in is that it may be useful to autogenerate
part of MANIFEST from CVS and add or remove some specific files. If I
generate MANIFEST directly I'll have to create my own mechanisms for
this sort of thing and lose some of the automatism distutils provides.

> If a MANIFEST file contains its own name, it is also included
> in the source distribution. (People who want to run another sdist on 
> this unpacked distribution would use this file. Except there is a 
> newer MANIFEST.in file.)

Ok. That's a solution to that part of the problem.


I think for a start I'll write my own sdist command as an extension of
the standard sdist that simply builds the MANIFEST file and then calls
the base-class' run method.

Thanks,

   Bernhard

-- 
Intevation GmbH                                 http://intevation.de/
Sketch                                 http://sketch.sourceforge.net/
MapIt!                                               http://mapit.de/