2013/6/26 Marc Davenne <marc.dave...@cramif.cnamts.fr>: > Hi there. I have a question about subversion. > > I have a theory on what files should not be on SVN and I would like you to > tell me if you agree. If you dont agree can you tell me why please. If you > see more files that should not be there, tell me and why. > > Files who should not be on SVN : > > files automatically generated > > files containing specific information about my development environment (so > properties files for example) > > executable files > > PS: I am conscious that we can put anything to subversion but I am looking > for Best practices > > Thank you so much
"Files that should not be on SVN" is like "food that should not be in a restaurant". It depends tremendously on your purposes. For example, a "tag" with locked down binaries, or installable packages, can be very useful for controlling what binaries are deployed in some environments. They're not efficient to store, however, and if there is a lot of "churn" of testable or development binaries, the record of them can get out of hand. It can be very efficient for a source tree for building software to avoid ".o" files, ".a" files, and other geneerated compilation productions that are not part of hte source code itself. But I know plenty of Subversion and other source control systems where developers store the ".jar" files from java, or store critical binaries for full software deployments. Perhaps you can describe your use case? That affects best practices profoundly.
