If the code is in CVS, you can define this in your GNUmakefile (or something similar):
NAME=MyApp PACKAGE_NAME=$(NAME) CVS_MODULE_NAME = gap/user-apps/$(NAME) CVS_TAG_NAME=$(PACKAGE_NAME) and then do just make cvs-dist There are also similar definitions for svn (and make svn-dist) On Jun 9, 2010, at 2:36 PM, Riccardo Mottola wrote: > Hi, > > maybe this time I just run "make clean" instead of "make distclean" before > running "make dist". > > I wonder if it might be be possible to always run make distclean before > creating the tarball, directly by default by gnustep make. Once I had a .core > file inside a dist which bloated it! > Could this have unwanted consequences? > > Riccardo > > Yavor Doganov wrote: >> Congratulations! I'll file an ITP to get this into Debian. >> >> One minor remark. The tarball has autosaved files: >> >> ya...@keel:/tmp/Graphos-0.1$ find -name '.#*' >> ./.#GNUmakefile.1.9 >> ./.#GNUmakefile.1.4 >> ./.#GRBezierPathEditor.m.1.6 >> ./.#PC.project.1.11 >> ./.#GNUmakefile.1.8 >> ./.#PC.project.1.16 >> ./Resources/GRDocument.gorm/.#data.info.1.1 >> ./Resources/GRDocument.gorm/.#objects.gorm.1.2 >> ./.#PC.project.1.17 >> >> This junk is causing us trouble. BatMon has an even more serious issue >> since it has object files. It is a good idea to run `make distclean' (or >> even better: cvs export) before `make dist' and make sure all these files >> are removed... >> >> >> > > > _______________________________________________ > Discuss-gnustep mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/discuss-gnustep _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
