Describe the db/ format

[Tim Lebedkov]

please provide a formal description of the repository as seen here:

https://bitbucket.org/vimcommunity/vim-pi/src/5bb9da5db0ce0ad0c19be2e9d0954f826db784a6/db/?at=master

[glts]

The initial comment in the script python/autoget.py lists the files and their purpose. I think the documentation is ok, but it's a little hard to find. Maybe we can improve this.

[Tim Lebedkov]

I could adapt and contribute this file from Npackd: https://code.google.com/p/windows-package-manager/wiki/RepositoryFormat How should this be done?

[Tim Lebedkov]

could anybody please answer?

[marco-oweber]

In my private mail reply I told that we're waiting to see what neovim turns into. Additionally we use the following sources: a) vim.sf.net b) install instructions from a to find github repositiories (and the like) c) manually contributed ones d) dr chip.

vim-pi wants to be one source of plugins (in the future) - thus we had in mind deriving debian/gentoo/ubuntu/nixos/npackd package descriptions from this database. Now reading your text I feel we should discuss in which way syncing should be done. from vim-pi to npackd or the other way round (which is what I think you suggest?)

[Tim Lebedkov]

No, I do not suggest to synchronize from the Npackd database to this one. I just feel that it is necessary to have a well-defined format for such a database of packages (I call it repository). This way it would be possible to have multiple repositories hosted by different parties.

[Tim Lebedkov]

I created a simple package database format description: https://bitbucket.org/vimcommunity/vim-pi/wiki/PackageDatabaseFormat The only thing that I removed was "vim_script_nr":4904 as it seems to have no real value for a package manager in Vim.

How can this be approved by all project members?

[ZyX_I]

@tim_lebedkov This cannot be version 1.0. Check out https://bitbucket.org/vimcommunity/vim-pi/issue/80/create-some-kind-of-api-which-makes-vim-pi, there I have a proposal how vim-pi database should look like. Also note that vim_script_nr is actually used value, it makes it possible to compute plugin homepage.

[Tim Lebedkov]

you're right. #80 is very similar to this one. I'll post my comments there. I would even suggest to merge this issue with #80.

[ZyX_I]

Duplicate of #80.