That assumes that what is in svn is what is in the tarball.
In practice, the packaging system needs to do various things.
For example, copying in the LICENSE file, checking newlines are all
unix, adding ppport.h if needed, and so on.
Adam K
Nik Clayton wrote:
Adam Kennedy wrote:
Since I moved to SVN, one of the things I've been doing is commiting
my release tarballs into a /releases/ directory.
One side-effect of this is that even before I've uploaded it to CPAN,
ever release already has a URI.
Eugh.
Have you considered using SVN::Notify::Snapshot to build the tarball
automatically instead?
N
