The Stackage project provides a cabal.config which locks in a specific
package set. This file should be shared between developers project so
that everyone is developing using the same versions of packages.
In addition to `.Spotlight-V100` and `.Trashes`, the following dotfiles
may appear at the root of all OSX volumes (not just external disks):
- `.DocumentRevisions-V100`: auto-save and versions storage
- `.fseventsd`: file system event storage
- `.Temporaryitems`: temp directory used by some applications instead of
/tmp and /var/tmp
- `.VolumeIcon.icns`: storage of custom icon for volume, if set
This directory is created by ExtUtils::MakeMaker starting with version
7.05_05, via this commit:
b6a9eba5b0
It was added to the default MANIFEST.SKIP in ExtUtils-Manifest 1.70, here:
e0f44577f8
Fixes#1217.
Once again ignore .classpath and .project in the Eclipse template. This has
been requested in multiple PRs such as #1338 and #1221 and is essentially a
reversion of #805. I copy the explanation for this change from the discussion
in #1217 by @segfly:
*In short*:
I can't point to any counter-documentation off the top of my head. I just know
from experience these files pollute a project's repo without adding value
- that is, unless everyone contributing is using Eclipse and no-one is using
dependency management. And even then, the guidance provided by the eclipse docs
is bad advice.
*In Long*:
The .classpath file is used by Eclipse to maintain the project's classpath
during automatic compile (every save of a file). In the olden days, one would
manually configure the project within the Eclipse UI and include all the
dependent jars necessary to compile your project. Eclipse then wrote that
configuration out to the .classpath file.
In theory, this file could be shared with others so they did not have to
manually configure their eclipse classpath. In practice, I never saw it work
out quite so well due to eventual bloating of the classpath with needless jars
or jars that only existed on one person's machine. Mind you, many people back
then also used to check their dependent jars into version control along with
their source.
Dependency management tools like Gradle and Maven have done away with all that
of course. But they also integrate nicely with Eclipse and manage the project
classpath dynamically. The .classpath file is basically rebuilt based on
changes to the build.gradle file or pom.xml file. Effectively, this renders the
whole point of checking in the .classpath moot as it is easily rebuilt by the
Maven or Gradle plugin.
The .project file is another animal completely. It basically describes what
plugins should be applied to the project as configured in the Eclipse UI. Again
the theory is it could be shared and creates a happy world. But due to
different eclipse versions people may have, different plugins installed, etc.
sharing the .project file actually causes more issues. And I've seen many
projects unable to open due to a bad .project file - requiring one to delete it
anyway (which then of course, when someone recreates it, they inevitably check
it in over the old one and end up breaking someone else's environment).
The bottom line is, regardless of what the eclipse documentation says, these
are very much internal configuration files for eclipse and best left out of
a repo.
Carl Suster