in reply to What's in a Repo?

I want to get all files that I need for building the distribution: Build.PL/Makefile.PL, lib/ and t/, maybe a README, maybe a document on hacking, maybe examples.

If the distro needs it, additional art work, images, files for a web page.

I don't want non-working code anywhere in the repo. I don't want any notes that nobody except that author can understand. And I want tests in t/ directly, as is custom for Perl modules.

Perl 6 - links to (nearly) everything that is Perl 6.

Replies are listed 'Best First'.
Re^2: What's in a Repo?
by Xiong (Hermit) on Aug 07, 2010 at 11:54 UTC

    How does your list of wants differ from the final CPAN tarball?

    Again, please choose an imaginary role for yourself, to put your comments in context.

    All tests of DC are in t/ and all files in there are tests; the files in folders with similar names are things that didn't make it: bad ideas, incomplete ideas, or tests that apply to another module, for comparision.

    Note: Contents may change.
[reply]
[d/l]
[select]
      How does your list of wants differ from the final CPAN tarball?

      I don't need generated files like MANIFEST or META.yaml.

      All tests of DC are in t/

      I had the impression they were in run/t/. Maybe I mis-read your initial post.

      Update: If it wasn't clear before: for me a release is a snapshot of a repository at a certain point, plus generated files (if necessary). As such I think that the repository structure should closely follow the structure of a CPAN distribution.

      Perl 6 - links to (nearly) everything that is Perl 6.
[reply]
[d/l]
        the repository structure should closely follow the structure of a CPAN distribution

        Thank you moritz++. I was beginning to believe I had lost my sanity.

[reply]

In Section Seekers of Perl Wisdom