On Wed, 2009-02-25 at 22:40 +0100, Pascal Craponne wrote: > no, there is no IRC channel.
Should we start one? Or is there no interest among the current maintainers? If there is interest, I would suggest starting a ##dblinq channel on freenode. This would require registering the channel; directions can be found at: http://freenode.net/group_registration.shtml > Regarding the tests, I have no specific idea about how the directories > should be organized (and since I'm the only one to answer to you, I > must be right :)). > The remaining problem is: where should the common tests (95% of them) > be placed? > If you choose a structure under a common directory, as you suggested > as second option, the problem is probably easier to solve. I don't think the shared files require the second solution. :-) To prove so, I've created a new branch: https://dblinq2007.googlecode.com/svn/branches/tests-without-db/ In this branch, I've committed the previously suggested test split, so that tests are located within a src/Assembly/Test directory. Shared files are located within src/DbLinq/Test/Providers. The .csproj, .vbproj, and .sln files have been updated to cope with this change. That's the good news. The bad news is that I only have Visual Studio Express to play with, and loading the DbLinq.sln file throws up a ton of error about the project files using features that aren't supported within Express, so I would appreciate it if someone else could take a peek and ensure things are still sane. (A subset of DbLinq.sln is supported in Express, so I was able to build most of the projects, but I don't know that all of them will build.) This brings me to a related issue: file duplication in the build process. At present, all the project files are setup so that they copy dependent assemblies into their output directories (which makes sense, as this allows the assemblies to actually work properly ;-). Unfortunately, for my DbLinq.sln-under-Express build, this results in 18 copies of DbLinq.dll running around, which seems...excessive. Similarly, there are 3 copies of DbLinq.SqlServer.dll, 4 of DbLinq.Oracle.dll, 5 of DbLinq.Sqlite.dll.... We could greatly reduce all this duplication by configuring the projects to place their output files into a common directory, e.g. into the top-level lib directory (which also contains Npgsql.dll, etc.), or perhaps into a src/build directory. (Personally, I'd prefer throwing them into the toplevel `lib' directory, but that's just me...). Would this be a reasonable change to make? Or is the current setup preferred? Thanks, - Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DbLinq" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dblinq?hl=en -~----------~----~----~----~------~----~------~--~---
