Ritu Kamboj wrote: > Jan S Berg wrote: > >> Jyri Virkki wrote: >> >>> Ritu Kamboj wrote: >>> >>>> The mysql-test directory exist in a typical MySQL release area. >>>> >>>> I would recommend that we merge the contents of mysql-test to >>>> SUNWmysql5usr package. >>>> >>> I'm still curious to know how commonly (if ever) end users need the >>> test suite? What are the use cases? >>> >>> If sometimes (or more often), combining into SUNWmysql5u package sounds >>> good. >>> If hardly ever, maybe a separate package is better so it can be removed >>> by those who don't need it. >>> If never.. don't package it. >>> >>> Also, how much content is there? That should also influence your >>> decision. If it's only a few executables, doesn't make that much >>> difference. If it is thousands of rarely-used files, a separate >>> package starts looking better. >>> >> There are quite a few files, so having it as a separate package sounds >> ok with me, >> but as I think there could be some use of them it would be nice to have >> them available at least. > > if we decide to have a seperate package for mysqltest, than we can have > everything under mysql-test and sql-bench directory in that package. > > I agree with you that since mysql-test and sql-bench directories are > components of typical mysql release directory, we should also made them > available.....
Yes, I believe that is a good idea - separate out the test related deliverables in a package of their own. We had the same concern with Java DB (Apache Derby) where the Derby distribution will hog a considerable amount of disk space for Derby test binaries and files of less interest to the majority of application developers than to the Derby developer community, and left it out of Java DB distibutions. You may want to consider this for MySQL. -- Lars
