On Wed, Apr 18, 2007 at 01:13:02PM -0700, Cameron Dale wrote: > On 4/18/07, Mike Mestnik <[EMAIL PROTECTED]> wrote: > >Package: torrentflux > >Followup-For: Bug #399150 > > > >I'm trying to use sqlite as the DB, as it's better(smaller). > > > >http://www.torrentflux.com/forum/index.php?topic=697.msg6285 > > If you're referring to the possibility of removing the dependency on > php4/5-mysql, I don't see that happening anytime soon as it is > required for torrentflux to work properly as packaged. It is certainly I do love to finish installing a pkg only to find it's ready to be used. I understand the current dependency on php4/5-mysql is required for this to function, but then I see that you are missing dependences for this goal. dbconfig-common blows up even after trying to disable it's use and eventually mysql is called, falling as it's not installed.
> possible to run torrentflux using any database server supported by > adodb, so you should have no problem using the source from > www.torrentflux.com to get it working using the instructions you > linked to. Otherwise, you could try to just install the package with > minimum dependencies and no database, and then modify it using the > instructions you provided. (Note that you don't need to install a > mysql server or stand-alone client, only the php4/5-mysql package and > its dependencies.) > I think it would be safe to change this, since you will not make it past the install without a stand-alone client and presumably a mysql server. Please consider only suggesting the use of mysql. This problem is general enough that a general solution might work well. What would this pkg/app requirer to be non-DB dependent? I'm thinking a common/root SQL syntax that can be compiled(fixed up) to run on many target DBs. A method to return the information needed to connect to these *arbitrary* DB systems, so the pkg could create a working config file that would work with both an app and libphp-adodb. A "common" pkg that would ask the debconfg questions to define the database and initialize it, dbconfig-common sounds like a good name. > I would have to add sqlite support to the package before the > dependency could be dropped. Integrating this into the package is more > complicated than it seems, and so supporting multiple database > backends is kind of low priority right now. I suggest you open a new > wishlist bug asking for sqlite support to be added, although I was > thinking the first other database I would try to support would be > postgre. > > Thanks, > Cameron -- /**************************************************************** * Mike Mestnik: Junior Admin 612-395-8932 * * [EMAIL PROTECTED] VISI/Digital North * ****************************************************************/ Alt address: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
