Default exclude list for cargo --new

[behnam]

It recently came up that cargo packages are not expected to publish tests, in addition to other development-related materials. (servo/unicode-bidi#43)

So, the question is shouldn't cargo --new have the exclude list already populated with test/*, banches/*, etc?

Having it would make publishing new crates faster by helping newcomers with getting it right easier and learning what needs to be done for publishing.

What do you think?

[steveklabnik]

It recently came up that cargo packages are not expected to publish tests,

I think that's a bit strong. I've never heard of anyone doing this until this thread!

[alexcrichton]

Yeah I don't think that we'd want to do this by default, some crates have no problem publishing tests while others have megabytes of tests that don't need to be published. I wouldn't say there's a concrete recommendation one way or the other here.

[behnam]

Cool! So the original assumption here was my misunderstanding of the common practices. Do you think it's worth mentioning this somewhere in the docs? Where would be a good place for it?If so, I can try submitting a PR for that. Otherwise, we can just close this then.

[alexcrichton]

I'm always fine with mentioning stuff in the docs, although I don't know offhand where this'd go. Somewhere in src/doc most likely, so feel free to throw it in there if you find an appropriate place.

[behnam]

I'm going to write up a sentence for this section: http://doc.crates.io/crates-io.html#before-publishing-a-new-crate

[alexcrichton]

👍