1. Mailing Lists
  2. Contributors
  3. Re: OCA Addons Packaging next step

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Should we use the new GitHub reactions?

AUTO: Kevin McMenamin is out of the office (returning 14/03/2016)

Avatar

Re: OCA Addons Packaging next step

by
ClosingAp Open Source Integrators Europe, LDA, Daniel Reis
- 11/03/2016 18:16:11

Great to see this go ahead Stéphane!

A few questions:

a) I would prefer to have a ".setup" directory name instead of "setup".  Is this viable?
b) I also couldn't find the setup.py file in the  acsone/account-financial-reporting repo. Did i miss something?
c) How will the "setup" directory be kept up to date? An additional task for the OCA bot?

 

/DR


Citando Bidoul@pad.odoo-community.org:

Dear contributors,
 
Following this blog post [1] about packaging and installation of OCA addons, I would like to take two next steps:
 
1. add the setup.py files to all OCA repositories
 
Step 1. consists in adding an unobtrusive setup directory in each repository. I plan to do this with a mass commit using setuptools-odoo-makedefault [2]. 
 
An example of such an autogenerated setup directory can be found in branch [3].
 
After that, we will have the possibility to manually fine-tune the setup.py for specific refinements (such as having more precise version dependencies or grouping some glue autoinstallable modules in the same package as their main module). 
 
After these steps are done, I will prototype a mechanism to upload the wheels to pypi.
 
Do you agree?
 
-sbi
 
Stéphane Bidoul | @SBidoul
Acsone sa/nv | http://acsone.eu/ | +32 2 888 3120
 

_______________________________________________
Mailing-List: http://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: http://odoo-community.org/groups?unsubscribe


 

Reference