Regarding these files that people forget to checkin. Doesn't every project have a well define directory structure? Shouldn't the "prefs/boring" file use this fact to encapsulate the rules of file inclusion and exclusion? Isn't it safer to checkin too many files (by accident) than forgetting one? Shouldn't this behavior be the default?
To me version control also means "if it works on my machine, it should work on all other peoples machines after they are in synch". Of course in reality people can also have different environment variables, different versions of operating systems, different hardware, etc so this idea certainly is utopia (however the version control system "VESTA<http://sourcefrog.net/weblog/software/vc/vesta/index.html> " tried to version everything, they even considered versioning the operating system :-) On Fri, Apr 3, 2009 at 11:23 AM, Malcolm Wallace < [email protected]> wrote: > > > Thus the uploaded sdist was missing one of the source files, and > > > consequently failed to build. > > > > I have a pre-release make target where I test everything I can think > > of. I think it prevents the above, am I right ? > > Not unless you run 'make check' in a separate pristine copy of the repo. > > The problem occurs when your local development repo contains some > essential files that have not been checked into the VCS. Your 'make > check' will work fine for you, but not for other people. > > Regards, > Malcolm > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
