[yacoob@hell.pl: vim policy]

[Stefano Zacchiroli]

--UugvWAfsgieZRqgk
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[ added in Cc Michael Piefel, co-maintainer with me of the vim-scripts
  package, since I don't know if it is subscribed to this list. Michael:
  we are discussing a proposal of debian-vim policy for packaging of vim
  scripts ]

On Sun, Jun 05, 2005 at 11:43:34PM +0200, Norbert Tretkowski wrote:
> 2. Vim startup.
>=20
> Vim should automatically source all scripts added into /usr/share/vim/add=
ons.
> We believe that IF site administrator is installing a script system-wide,=
 from
> a package, THEN this script is considered important and is meant to be so=
urced
> automatically. Therefore, administrators should think twice before instal=
ling
> a script in this way.=20

I don't like the application of the IF ... THEN policy above for vim
scripts. An editor like vim is an higly customizable piece of software
and in my experience no two users use the same settings. It is thus
reasonable to think that a system administrator of, say, a cluster of
machines will install a plethora of vim-* packages so that they are
available to users.

Thus I propose to have at least a debconf question which asks sysadm
whether i wont the scripts available to all users or not. In my opinion
debconf answer will be used to decide how to invoke your vim-install
utility.

> If the particular user does not share this point of view, he has the opti=
on to
> change this behaviour, by removing /usr/share/vim/addons from the runtime=
path.
> It can be accomplished by setting runtimepath in his or her ~/.vimrc.

I would like to have the two options available: if the sysadm choose to
make a scripts available to every one then single users could inhibit
it + the other way round: if the sysadm choose not to make a script
widely available single users could enable it.

Single users actions in my idea should be performed using vim-install.

> http://yacoob.dnsalias.net/sakwa/vim-install
> It should be included into vim package.

Agreed. BTW does vim-install handles scripts which need more than one
file to be installed/linked?

> 4. Help files handling and helptags generation.
>=20
> All scripts documentation should be put in compressed form in
> /usr/share/vim/addons/doc directory. A script that will generate helptags=
 file
> for this directory has been written and is available at:
>=20
> http://yacoob.dnsalias.net/sakwa/helpztags
>=20
> It should be included into vim package. All packages containing vim scrip=
ts
> with documentation should pre-depend on vim.

I noticed that many scripts generate documentation on-the-fly the first
time they are executed. Usually this first execution installs generated
documentation in home dir. Do you know how to avoid this? We of course
don't want to have a script shared by all users but a per-user copy of
the generated documentation ...

> Currently, only vim-latexsuite conforms to this point.

Anybody knows which other packages need to be patched? IIRC vimoutliner,
others?

> 7. vim-scripts package.
>=20
> This package is intended to act as a 'bag of scripts'. Scripts in this pa=
ckage
> are NOT put into /usr/share/vim/addons/, and thus are NOT enabled by defa=
ult.
> If user (or administrator) wants to enable one of the scripts from vim-sc=
ripts
> package, he should copy it to specific directory (i.e. ~/.vim/).

Could we reuse vim-install for this?

Many thanks for your work!

Cheers.

--=20
Stefano Zacchiroli -*- Computer Science PhD student @ Uny Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it} -%- http://www.bononia.it/zack/
If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. -!-

--UugvWAfsgieZRqgk
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCpBED1cqbBPLEI7wRAoP9AKDEsity49A2S2TnIdp6sEDe4TIJhQCgwo3G
L6d4XNVXdcHQgPLdH5Q55bE=
=yH5E
-----END PGP SIGNATURE-----

--UugvWAfsgieZRqgk--