Hi, That naming convention is due to the fact that there was a time when Monticello committed the content of packages based on prefix matching. So, if you had: FileSystem-Core FileSystem-Core-Tests committing FileSyste-Core would also commit FileSystem-Core-Tests as a subcategory. Actually, we still have the bug that if you would change something in FileSystem-Core, FileSystem-Core-Tests would be marked as dirty. Still, it would be much better to have naming of a package reflect a categorization. So, FileSystem-Core-Tests would be much more preferable. Cheers, Doru
On Sep 4, 2016, at 10:17 AM, stepharo <stepharo@free.fr> wrote:
Hi guys
Sorry to be that dull and stupid but I do not get why (beside following the seaside convention - and I do not understand it either) why the test package for FileSystem-Core is named FileSystem-Tests-Core
and not just
FileSystem-Core-Tests
like that we could have
FileSystem-Core-Help
FileSystem-Core-Examples
And when we are looking for FileSystem-Core we can see automatically FileSystem-Core-Tests
Now we cannot.
Stef
-- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."