1. Mailing Lists
  2. Contributors
  3. Re: Repo Metadata

Contributors mailing list archives

contributors@odoo-community.org

Browse archives

Re: Repo Metadata

Re: Repo Metadata

Avatar

Re: Repo Metadata

by
dar
- 28/06/2019 13:34:57
Still no decision on this one, but as odooup now has a dependency analyzer, in reality, the dependency metadata needs proper URI naming scheme.
Like so: github.com/OCA/rest_framework instead of rest_framework.

Else building a proper DAG tree is a headache, when just having the starting point at hand.
Also alternate implementations would become within reach...

My lobby force in Odoo SA is limited. Anyone happy to help?!?

On Sat, Jun 22, 2019 at 9:42 PM David Arnold <dar@xoe.solutions> wrote:
Ok, so. As general acceptance is still far beyond what I expected, let's just move on to discussing the most useful data structure for a while...

And which Microservice to use to host the sync function? Travis! Travis! Travis! 

Hey, but there are Amazon lambda functions (remember the scalability argument), and other buzzy things, too.

Hosting the data structure, GitHub seems just fine, though...

El sáb., 22 jun. 2019, 2:27 p.m., David Arnold <dar@xoe.solutions> escribió:
And lets be honest, this representation would be useful on a far broader scale than what can be covered by ~/.cache

This is why the academy is left to argue with current priorities and resource constraint...

Btw, how do promotions work, if resource constraint and current priorities are such an issue?

El sáb., 22 jun. 2019, 2:21 p.m., David Arnold <dar@xoe.solutions> escribió:
I don't know what my XY problem is. ;-) But it looks like it doesn't even trigger an immune reaction...

Jokes aside. 

I'm still undecided about the final claim I should formulate (or if at all) for the academy ;-)

- While GitHub API is most ubiquitous across the community.
- Metadata indexing is lacking quality

Maybe I should claim hosted metadata compounding URI namespaces + module manifests (for example to be able to programmatically infer dependency).

El sáb., 22 jun. 2019, 12:57 p.m., Nhomar Hernández <nhomar@vauxoo.com> escribió:


On Sat, Jun 22, 2019 at 4:12 AM Georg Notter <georg.notter@agenterp.com> wrote:

On the last OCA sprint, creating the OCA APP Store we were already thinking of this.



I do not want to be rude but the instrospection is the way to go, Why? because it si the python way (and it takes litelrally 20 lines of code to do it we did it) it is generic enough and you can use even generic repositories from third parties [http://www.odoo-code-search.com/ does this since years ago and they are not bothering to ask for change in each community asking new features, because it is almost impossible to achieve, the OCA is one repo of code, we can finde now tens of teams open sourcing nice stuff].

If you want to save let's say bandwidth. list the repos and try to find a __manifest__.py if there is one the try to install it.

This problem can be loved with pretty straight forward solutions like git sync.

That's how it works in almost all app-stores in the world, if not we will end up maitaining the index of the index of the index and at the end with a little black list for exceptions and a lit of indexes.

Cache is the tool: A declarative white/blacklist on each side you want to use it with your own included limitations (sizing, techncials installability).

What you need at the end is a list of **Installable things** trustable enough (that's the X) and to achieve that you can not relay 100% on the origin of the information (because we can not considere all the use cases), i.e.: we have in 100% of repositories the setup folder (for pip) you can use it as well as a helper.

I hope I explain myself better.

Regards.


 
It Would be great to have a well structured index of all Apps and so on.

Also for searching in the APP Store it Would be a Benefit.

Mit freundlichen Grüßen

We look forward to see you. Best Regards

Dipl. Ing. (Fh) Georg Notter

Agent ERP GmbH

www.agenterp.com

Am 22.06.2019 um 09:27 schrieb Georg Notter <georg.notter@agenterp.com>:


No, He Propperly described the use Case.

And he's right.

Mit freundlichen Grüßen

We look forward to see you. Best Regards

Dipl. Ing. (Fh) Georg Notter

Agent ERP GmbH

www.agenterp.com

Am 22.06.2019 um 07:47 schrieb Nhomar Hernández <nhomar@vauxoo.com>:



On Fri, Jun 21, 2019 at 8:12 PM David Arnold <dar@xoe.solutions> wrote:
OK, building local state then, if we can't agree on a well-behaved interface... :/ Damn it!

Our interface is a well-behave one, and we agree on that we disagree with you my friend.

You are having a tipical XY problem.


 

On Fri, Jun 21, 2019 at 8:04 PM David Arnold <dar@xoe.solutions> wrote:
>If you read, clean (with manifest) then cache on your side and then serve your own clean json is the way.

You give me an idea... I could do it at the module level, but I'd have to rely on git-subrepo.
history CAN be reconnected, but it-s not natively...

On Fri, Jun 21, 2019 at 8:02 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:


On Fri, Jun 21, 2019 at 7:57 PM David Arnold <dar@xoe.solutions> wrote:
Hehehe :D - Yeah! That's too much work for the modern Librarian! Books should come with an ISBN.

they actually does, but you want to create ISBN-xoe and that the academy does for you the dirty work... ;-) here it is called manifest.
;-)
If you read, clean (with manifest) then cache on your side and then serve your own clean json is the way.

On Fri, Jun 21, 2019 at 7:52 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
create a wired blacklist on your side.

On Fri, Jun 21, 2019 at 7:47 PM David Arnold <dar@xoe.solutions> wrote:
Well mostly because there are repos like:

And there was recently a python lib proposed on this mailing list.

While people would be stupid to select them when scaffolding a dev project as odoo mdule repos, it potentially can corrupt the scaffolding state.
I don-t want to implement code that could potentially corrupt state.



On Fri, Jun 21, 2019 at 7:42 PM Nhomar Hernández <nhomar@vauxoo.com> wrote:
why aren't you using github api¿? or the api from the CVS in charge of your code?


On Fri, Jun 21, 2019 at 9:56 AM David Arnold <dar@xoe.solutions> wrote:
Hi OCA,
Hi Pedro,

Would it be possible to maintain this file as a JSON data structure?


I'd like to automatically consume it by odooup to ease creation of OCA flavoured projects.

Would be cracking!

Best Regards,

David A.

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



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

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

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



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

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

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



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

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

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



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

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



--

--
Nhomar Hernandez
CEO Vauxoo.
Twitter: @nhomar
Odoo Gold Partner
Skype: nhomar00 (Envia mail previo no lo superviso siempre).
Móvil Venezuela:
+58 4144110269 (Telegram)
Móvil México:
+52 1 4773933942 (Whatsapp)

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

Reference