Bug 72204 – Manual page for vim-plugin.eclass

• Status: RESOLVED FIXED
• Product: Portage Development

[Description Aaron Walker (RETIRED) 2004-11-23 02:17:14 UTC]

attached

[Comment 1 Aaron Walker (RETIRED) 2004-11-23 02:17:35 UTC]

Created attachment 44537 [details]
vim-plugin.eclass.5

[Comment 2 Ciaran McCreesh 2004-11-23 08:02:09 UTC]

Hm, we might want to include some stuff about how to actually really make a vim plugin... We can't use upstream tarballs for this, so it's not entirely as obvious as one might think.

[Comment 3 SpanKY 2004-11-30 15:42:07 UTC]

well can you update the manpage with said considerations ? :)

[Comment 4 Ciaran McCreesh 2004-12-02 06:54:33 UTC]

Ok, I don't know whichever roff this is and I'm too lazy to learn, but I'll give you text :)

PACKAGING

In general tarballs for plugins cannot be used directly because of vim.org's idiosyncratic download system. Instead a Gentoo-specific tarball must be made with the following format for contents:

    packagename-version/
    packagename-version/doc/
    packagename-version/doc/whatever.txt
    packagename-version/plugin/
    packagename-version/plugin/whatever.vim
    packagename-version/syntax/
    packagename-version/syntax/whatever.vim

PACKAGE NAMING CONVENTIONS

Where possible, the upstream script name should be used as the package name. For packages which provide syntax or filetype files, the name should be suffixed with "-syntax" (for example, "app-vim/gentoo-syntax", "app-vim/fluxbox-syntax", "app-vim/selinux-syntax").

PACKAGE VARIABLE CONVENTIONS

The canonical form for the HOMEPAGE variable for vim.org scripts is "http://www.vim.org/scripts/script.php?script_id=123".

[Comment 5 Aaron Walker (RETIRED) 2004-12-03 08:23:47 UTC]

Created attachment 45207 [details]
vim-plugin.eclass.5

revised.

[Comment 6 SpanKY 2004-12-16 19:51:51 UTC]

ciaran: so we all set now ?

[Comment 7 Ciaran McCreesh 2004-12-16 21:51:14 UTC]

sure why not

[Comment 8 SpanKY 2004-12-16 21:56:19 UTC]

in cvs