I personally wouldn't mind that a dependency on mysql-server is added to the mythbackend. It'll only make my rpm-find-requires output shorter by one line :-)
On 1/23/07, Guillaume Rousse <[EMAIL PROTECTED]> wrote:
Stefan van der Eijk wrote: > On 1/22/07, *David Walluck* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote: > > Guillaume Rousse wrote: >> The problem is mainly to cover the various kind of setup here: > local or >> remote database server, password-protected database administrator >> account, etc... I don't even consider the mysql vs postgresql case > (most >> apps are mysql only), nor the distribution installation scenario (you >> won't be able to even start the server). Current consensus is that a >> good description of a manual procedure is better as an half-baked >> technical solutions. > > I wouldn't say half-baked, but partial. I know that no solution can > cover anything. So, are you saying that even if we consider just the > local mysql, local pgsql, and sqlite cases that this would be pointless? > > >> I think that only the default option should be supported out of the box. >> In the case of mythtv this is likely to be a local mysql server. Having a partial solution is OK, as long as it doesn't add undesirable side-effects. Here this would requires a dependency on mysql-server, which we don't want, because it would force its installation for everyone. _______________________________________________ PLF-discuss mailing list [email protected] https://www.zarb.org/mailman/listinfo/plf-discuss
_______________________________________________ PLF-discuss mailing list [email protected] https://www.zarb.org/mailman/listinfo/plf-discuss
