please remove .cvsignore files from tarballs

Comments

rsevero’s picture

rsevero commented
Assigned: Unassigned » rsevero

Please help me here.

Is there a way to set some files to be ignored in CVS and not have the .cvsignore files? Or are you saying that I can't use the "ignore" feature of CVS? If so, why?

btbroot’s picture

btbroot commented

No, it's actually your release script work. Basically what you do when you're releasing is:

1. cvs export ...

2. tar czf ...

You can exclude VCS files (.cvsignore), backup files (*.~ *.bak) etc on the step 2 from being included in the release tarball just by --exclude=PATTERN option.

rsevero’s picture

rsevero commented

Thank you. I will do it ASAP.

rsevero’s picture

rsevero commented
Status: Active » Postponed (maintainer needs more info)

Files removed by http://drupalcode.org/project/charts_graphs.git/commit/6060be9

I want to create .gitignore files with the same use of the .cvsignore ones I just deleted.

After reading carefully your suggestion on how to deal with VCS files I'm still at a loss. You mention a "release script". AFAICT I don't have one. I can create one but I'm not sure how would it work.

With cvs after committing all changes I just tagged the selected version and then I create the new release in drupal.org. I haven't done a new release with git yet but I believe the process will be similar. Where does a release script enters this release flow path?

rsevero’s picture

rsevero commented
Status: Postponed (maintainer needs more info) » Fixed

As a future reference for me or others that face this same VCS files issue:

To use the ignore feature of your VCS without actually including the .gitignore file on your Drupal release you just have to ignore the ignore file, i.e., include a ".gitignore" line (without the quotes) on each .gitignore file.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.