bl-odoo 0.3.10

A command-line tool for managing Odoo dependencies.

bl

Why BL

Because ak is a bit slow and I was tired of waiting around

Install

pipx install bl-odoo

Usage

For all those command bl will try to look in the current directory. If it does find the spec file it will try to look in the child odoo directory. (i.e. you can launch bl in the root of you project) You can also override the default paths and verbosity with:

• -c/--config: path to the project spec file (default: spec.yaml)
• -z/--frozen: path to the frozen spec file (default: frozen.yaml)
• -j/--concurrency: number of concurrent tasks (default: 28)
• -w/--workdir: working directory, defaults to the directory of --config
• --log-level: one of DEBUG, INFO, WARNING, ERROR, CRITICAL (default: WARNING)

Build

bl build [-c PATH_TO_SPEC] [-z PATH_TO_FROZEN] [-j CONCURRENCY] [-w WORKDIR] [--log-level LEVEL]

What does it do

It does what ak build does

Params

• PATH_TO_SPEC path to your spec (default: spec.yaml)
• PATH_TO_FROZEN path to your frozen spec (default: frozen.yaml)
• CONCURRENCY number of module clone simultaneously (default: 28)
• WORKDIR working directory; if omitted, the directory containing spec.yaml
• LEVEL log level (see --log-level above)

How it looks

Freeze

bl freeze [-c PATH_TO_SPEC] [-z PATH_TO_FROZEN] [-j CONCURRENCY] [-w WORKDIR] [--log-level LEVEL]

What does it do

It does what ak freeze does

Params

• PATH_TO_SPEC path to your spec (default: spec.yaml)
• PATH_TO_FROZEN path to your frozen spec (default: frozen.yaml)
• CONCURRENCY number of module clone simultaneously (default: 28)
• WORKDIR working directory; if omitted, the directory containing spec.yaml
• LEVEL log level (see --log-level above)

Clean

bl clean [-c PATH_TO_SPEC] [-w WORKDIR] [--log-level LEVEL] [--i-am-stupid] [--dirty]

What does it do

By default it asks you if you want to delete external-src and src under the workdir and then deletes them. With --i-am-stupid it deletes those directories without prompting. With --dirty it additionally scans all repos in the spec for dirty git state and offers to clean them with git reset --hard.

Params

• PATH_TO_SPEC path to your spec (default: spec.yaml)
• WORKDIR working directory; if omitted, the directory containing spec.yaml
• LEVEL log level (see --log-level above)
• --i-am-stupid delete src and external-src non‑interactively
• --dirty also inspect repos and optionally clean dirty ones with git reset --hard

Odoo is taking a really long time to clone

Yes !

You can add a locales entry to your odoo repo in spec.yaml like so:

odoo:
  modules:
    - account
    ...
  remotes:
    odoo: https://github.com/odoo/odoo
  merges:
    - odoo 14.0
  locales:
    - fr
    - en

It will only download the french and english translation instead of all of them

• without locales: 849MB and 40 seconds fresh build
• with locales fr, en: 169MB and 27 seconds fresh build

⚠️ WARNING: you must list all the odoo modules you need if you use the locales property

I have warnings about patch globs

There is a new property to handle git am <patch_glob> (the old one still works but I hope to remove it at some point)

Before:

folder_name:
  modules:
    ...
  remotes:
    ...
  merges:
    ...
  shell_command_after:
    - git am ../../patches/patch_folder/*

After:

folder_name:
  modules:
    ...
  remotes:
    ...
  merges:
    ...
  patch_globs:
    - ../../patches/patch_folder/*

Benchmarks

Ak benchmarks

Fresh install

Already cloned once

Bl benchmarks

Fresh install

Already cloned once

Results

Type	AK	BL
Cold	~100s	2 - 10x faster
Hot	3-20s	2 - 10x faster