Disabling the 'mysql' USEFLAG and building net-misc/mediatomb does not enable sqlite3. This results in the following: 2010-05-05 17:30:46 INFO: Checking configuration... 2010-05-05 17:30:46 ERROR: You enabled sqlite3 storage in configuration, however this version of MediaTomb was compiled without sqlsupport! I've attached an ebuild I hacked up quickly that enables sqlite3. I'm fairly new to the ebuild business, so the maintainer will probably want to do something different than I did, since I believe my fix will break configurations that want mysql? Reproducible: Always
Created attachment 230555 [details] ebuild that properly enables sqlite3
Hi, Please attach diff -u output.
Created attachment 230557 [details] diff of working ebuild As I mentioned in my original post, this was a quick hack just so I could install quickly. If someone tries to build with mysql enabled, this ebuild may enable sqlite3 as well and break stuff(?)
Ok, that diff is reversed but I get the point. What you are requesting is a sqlite3 USE flag such that you can use sql but not mysql, is that right? I don't use any sql in my setup.
(In reply to comment #4) > Ok, that diff is reversed but I get the point. > > What you are requesting is a sqlite3 USE flag such that you can use sql but not > mysql, is that right? I don't use any sql in my setup. > Actually, I don't get it. If you build mediatomb with -mysql, sqlite-3 is pulled in[1] *and* enabled in configure[2]. hmm [1]: !mysql? ( >=dev-db/sqlite-3 ) [2]: $(use_enable mysql) $(use_enable !mysql sqlite3)
clayton, Can you please run configure[1] and report what the configuration summary says about mysql and sqlite3? 1: ebuild /usr/portage/net-misc/mediatomb/mediatomb-0.12.1.ebuild configure
I also want to add that I was able to reproduce your error my building MediaTomb with mysql support. I then enabled sqlite and disabled mysql in config.xml. Since MediaTomb will fail to build if no SQL engine is present, it would seem that you haven't correctly disabled the mysql use flag. Can you double check package.use and make.conf to ensure the mysql use flag is disabled?
(In reply to comment #7) > I also want to add that I was able to reproduce your error my building > MediaTomb with mysql support. I then enabled sqlite and disabled mysql in > config.xml. > > Since MediaTomb will fail to build if no SQL engine is present, it would seem > that you haven't correctly disabled the mysql use flag. Can you double check > package.use and make.conf to ensure the mysql use flag is disabled? > I'd like to weigh in on this - I've been rebuilding mediatomb after every "world" emerge due to mysql being compiled in place of sqlite. I've done this by running "USE="-mysql" emerge -av mediatomb". My make.conf includes mysql but from my understanding package.use takes precendence. In summary, I believe that placing "-mysql" in package.use does not disable mysql from being built into mediatomb. Here is the config summary for the ebuild command you asked: sqlite3 : disabled mysql : yes libjs : yes libmagic : yes inotify : yes libexif : yes id3lib : disabled taglib : yes libmp4v2 : yes ffmpeg : yes ffmpegthumbnailer : disabled lastfmlib : yes external transcoding : yes curl : yes YouTube : yes libextractor : disabled db-autocreate : yes If you need any further information let me know. -- Nick
For ME: USE=-mysql ebuild mediatomb-0.12.1.ebuild clean configure <snip> CONFIGURATION SUMMARY ---- sqlite3 : yes mysql : disabled libjs : yes libmagic : yes inotify : disabled libexif : yes id3lib : disabled taglib : yes libmp4v2 : yes ffmpeg : yes ffmpegthumbnailer : disabled lastfmlib : disabled external transcoding : yes curl : yes YouTube : yes libextractor : disabled db-autocreate : yes USE=mysql ebuild mediatomb-0.12.1.ebuild clean configure CONFIGURATION SUMMARY ---- sqlite3 : disabled mysql : yes libjs : yes libmagic : yes inotify : disabled libexif : yes id3lib : disabled taglib : yes libmp4v2 : yes ffmpeg : yes ffmpegthumbnailer : disabled lastfmlib : disabled external transcoding : yes curl : yes YouTube : yes libextractor : disabled db-autocreate : yes So, I guess I don't get the problem here. If someone can explain it to me, I can surely make a change, but I'm pretty sure it should work as it.
