Community mailing list archives

community@mail.odoo.com

Re: OCA project: __unported__ folder considered painful

by
Camptocamp SA, Joël Grand-Guillaume
- 03/12/2015 04:56:16
I like your idea Graeme ! I've not think on it too much, but I believe it would improve the current situation !



On Wed, Mar 11, 2015 at 10:42 PM, Graeme Gellatly <gdgellatly@gmail.com> wrote:
How about just renaming _openerp__.py to __unported__.py?  I've not thought it all the way through but that would give

Obvious indication of not ported to users
Unable to install.
Cleaner Diffs, even if it might mess with __openerp__.py that is no big deal.
Forward ports etc.

Just an idea from reading others comments, not sure if it works or not.

On the 1 repo per module, I dream of the day git subtree (and subtree of subtrees) is easily and cleanly usable by mortals.  Adds a layer of management e.g. tagging which module version of subrepo is appropriate.

On Thu, Mar 12, 2015 at 6:38 AM, ICT Intranusa <ict@intranusa.com> wrote:

I try to capture the original of this thread, in a summary :

1. Is it posible to eleminate  __unported__ folder without lost link and WITHOUT change the current way
2. If yes, how?
3. If no, how to make it posible?

PM, Package manager? Even our youngest brother, PHP, with its PM and with baby age, COMPOSER, runing with happy, as I tried on solaris, windows, unix UX, bsd, mac & linux families.

Python PM? outside ubuntu family with specific version & kernel, super very PAINTFUL. On windows, harder on 64 bit SERVERS, I have to install SDK visual studio, drivers, and so many settings.

Odoo? As derivated product of python, we just can say keep encourage. Beside, we have totaly to keep linking with PostgreSQL RDBMS server.

On Mar 11, 2015 11:33 PM, "Nhomar Hernández" <nhomar@gmail.com> wrote:

2015-03-11 9:53 GMT-06:00 Raphaël Valyi <rvalyi@akretion.com>:

Now it's true with Odoo we don't have real python package and we don't have a Bundler yet. So IMHO it's okay to have a workaround for now,

HEllo Raph.

That's the escence of my PoV.

AND I should add only one thing:

In odoo we NEED take decisions so frequently commit by commit, the 10 years package management with with libraries that simply work or don't work and may be we have 15 days to solve a bug, in odoo I need verify even the procedure impact of a change, I think we need more time to mature such issues, but even if a package manager is developed I think I will never stop to use CVS to control my server, it is the unique way until now I can't find a correct versioning approach that repace my "pretty" sha ;-)

Regards, and also, I can adapt, but until now I think we must mature the information all of us manage.

I can share old bad POV about Gems and things that has bad for severalñ years also and almost impossible to one time they are fixed locally share in 2 commands and even Python normal pypi package manager, but I think it is point for other discusion.

Regards.
--
--------------------
Saludos Cordiales
 
--
Nhomar Hernandez
 

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe


_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe




--


camptocamp
INNOVATIVE SOLUTIONS
BY OPEN SOURCE EXPERTS

Joël Grand-Guillaume
Division Manager
Business Solutions

+41 21 619 10 28