[Python-apps-team] Bug#638720: packaging OpenERP

Dmitrijs Ledkovs xnox at debian.org
Mon Feb 25 13:41:32 UTC 2013


On 25 February 2013 12:52, W. Martin Borgert <debacle at debian.org> wrote:
> Quoting "Dmitrijs Ledkovs" <xnox at debian.org>:
>>
>> Blast from the past. Yeah sure, go ahead.
>
>
> Will do, thanks!
>
>
>> It would be nice to still package all of them & e.g. there is a 6.1
>> version of a package in ubuntu now.
>> But it's not as flexible packaged.
>> The openupgrade project has good migration scripts and it would be
>> great to integrate them into the packaging such that one can upgrade
>> from one major release to another.
>
>
> I suggest to package 7.0 first and than package 6.1 and openupgrade
> separately.
>
> I'm not 100% sure, how many people/companies can really make use of
> the packaged system anyway. ERP systems are much more than any other
> software customized versions, right? Having it packaged makes sense,
> because it makes sure that the software will build and run cleanly
> on Debian. And it can be used in simple cases and for demo purposes.
>

If there is a sensible way to override standard modules via
configuration file for web & server, I see know reason, why one cannot
use openerp from the archive and add/override modules as needed to
apply required modifications.

OpenUpgrade is trickier to integrate, as some facilities should be
provided for taking database snapshots upgrading & comparing / running
in parallel + fixups + custom migrations of custom modules etc.

Regards,

Dmitrijs.



More information about the Python-apps-team mailing list