On Tue, Nov 3, 2009 at 3:56 AM, gregor herrmann wrote:
> On Mon, 02 Nov 2009 07:15:35 +0100, Penny Leach wrote:
>
>> Well, that's logically equivalent to installing multiple versions of the
>> same package. At the moment, there's one moodle installation, which has
>> code that lives in /usr/shar
On Mon, 02 Nov 2009 07:15:35 +0100, Penny Leach wrote:
> Well, that's logically equivalent to installing multiple versions of the
> same package. At the moment, there's one moodle installation, which has
> code that lives in /usr/share/moodle, and connects to one database. This
> is determined
On Sun, Nov 01, 2009 at 12:25:51PM +0100, Penny Leach wrote:
> The problem we've come across is how to handle migrations. If we have a
> moodle package, that depends on moodle-mysql | moodle-pgsql, then package
> managers that just install the first dependency, could cause a situation,
> for examp
Hi,
On Sun, Nov 01, 2009 at 08:01:20PM -0600, Raphael Geissert wrote:
> First of all, why do you want to split moodle? there's for example phpbb3
> which uses dbconfig and allows multiple different DBMS as backends.
Fair question. There's also quite a few packages that depend on
dbconfig-common
Penny Leach wrote:
[...]
>
> I think the best way to handle this, is stop having a moodle package at
> all, but instead have a moodle-common package, that depends on either
> moodle-mysql and moodle-pgsql. These two obviously depend on
> moodle-common, and conflict with each other, and all three
[ please cc both me and the package team ]
Hi debian-devel
The Moodle package team is currently evaluating how to best upgrade the
existing not very well working, and out of date package.
Moodle is a webapp that works with both mysql and postgres. We currently
have a single package that supports
6 matches
Mail list logo
