Re: RFC: Filemaker packages

From: Date: Tue, 13 Dec 2005 00:30:58 +0000
Subject: Re: RFC: Filemaker packages
References: 1  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-40713@lists.php.net to get a copy of this message
On 12/12/05, Markus Amsler <markus.amsler@oribi.org> wrote: > Hi, > > I'm working on Filemaker database support through the Web Companion > interface (like FX.php[1], but better :-)). > The Filemaker database is not SQL-capable and stateless (no server > resultsets/resources). So it's a bit different then other DB drivers. > > My current plan is to make 3 Packages: > - FMPro > Basic Filemaker Web Companion Access (same functionality as FX.php) > depends on nothing > Files: FMPro.php, FMPro/Query.php > > - FMPro_SQL > SQL/resource emulation layer for FMPro (implements query, fetch, > free, ...) > depends on FMPro, SQL_Parser > Files: FMPro_SQL.php, FMPro_SQL/Query.php > > - DB_fmpro > PEAR DB driver > depends on DB, FMPro_SQL > Files: DB/fmpro.php > > Does this sound sensible? Should I open 3 different package proposals? > Can I depend on a package with state=devel (SQL_Parser)? > Any feedback is welcome. > > Pre-alpha source can be downloaded from [2]. > > Markus > > [1] http://www.iviking.org/FX.php/ > [2] http://oribi.org/pear/FMPro/FMPro.zip > Sounds useful to me as long as the licenses match up (if you copied form FX.php make sure to check the license in FX.php). As for the packages, they seem to make sense to me. Yes, a package can depend on an devel package just fine. -- Justin Patrin

« previous php.pear.dev (#40713) next »