Subject: Re: plan for spell files - msg#00250

Previous Message by Date: click to view message preview

Bug#365152: [yigal.weinstein@xxxxxxxxx: Bug#365152 - vim-latexsuite]

----- Forwarded message from Yigal Weinstein <yigal.weinstein@xxxxxxxxx> ----- From: Yigal Weinstein <yigal.weinstein@xxxxxxxxx> Subject: Bug#365152 - vim-latexsuite To: fpletz@xxxxxxxxxxxxxxx Date: Fri, 19 May 2006 12:18:04 -0700 X-Mailer: Evolution 2.6.1 I am in some need of a working vim-latexsuite. However even after applying the patch you provided in, http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=365152 /ref{} <F9> is not working- for me. 1. Have I applied the patch correctly all lines with a minus "-" prefix I deleted all lines with a plus "+" prefix I added to the desired areas - I think This is all I did 2. I am using vim-latexsuite/20060325-1 These are the vim files I have installed ii vim 7.0-017+2 Vi IMproved - enhanced vi editor ii vim-common 7.0-017+2 Vi IMproved - Common files ii vim-doc 7.0-017+2 Vi IMproved - HTML documentation ii vim-full 7.0-017+2 Vi IMproved - enhanced vi editor - full fled ii vim-gnome 7.0-017+2 Vi IMproved - enhanced vi editor - with GNOM ii vim-gui-common 7.0-017+2 Vi IMproved - Common GUI files ii vim-latexsuite 20060325-1 View, edit and compile LaTeX documents from ii vim-python 7.0-017+2 Vi IMproved - enhanced vi editor - with Pyth ii vim-runtime 7.0-017+2 Vi IMproved - Runtime files ii vim-scripts 6-3 plugins for vim, adding bells and whistles ii vim-vimoutliner 0.3.3-6 script for building an outline editor on top I am using debian unstable. Thanks Yigal Weinstein ----- End forwarded message ----- -- Franz Pletz \ Lots of the basis of the open source movement www: http://franz-pletz.org/ \ come from procrastinating students. email: fpletz@xxxxxxxxxxxxxxx \ -- Andrew Tridgell

Next Message by Date: click to view message preview

r690 - in /trunk/packages/vim-spellfiles: debian/control debian/control.in debian/copyright debian/rules patches/ upstream/

Author: zack Date: Sat May 20 06:03:37 2006 New Revision: 690 URL: http://svn.debian.org/wsvn/pkg-vim/?sc=1&rev=690 Log: snapshot Added: trunk/packages/vim-spellfiles/patches/ trunk/packages/vim-spellfiles/upstream/ Modified: trunk/packages/vim-spellfiles/debian/control trunk/packages/vim-spellfiles/debian/control.in trunk/packages/vim-spellfiles/debian/copyright trunk/packages/vim-spellfiles/debian/rules Modified: trunk/packages/vim-spellfiles/debian/control URL: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim-spellfiles/debian/control?rev=690&op=diff ============================================================================== --- trunk/packages/vim-spellfiles/debian/control (original) +++ trunk/packages/vim-spellfiles/debian/control Sat May 20 06:03:37 2006 @@ -2,7 +2,7 @@ Section: text Priority: optional Maintainer: Stefano Zacchiroli <zack@xxxxxxxxxx> -Build-Depends: debhelper (>= 4.0.0) +Build-Depends-Indep: debhelper (>= 4.0.0), aap, unzip, locales, quilt Standards-Version: 3.7.2 Package: vim-spellfiles-fr Modified: trunk/packages/vim-spellfiles/debian/control.in URL: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim-spellfiles/debian/control.in?rev=690&op=diff ============================================================================== --- trunk/packages/vim-spellfiles/debian/control.in (original) +++ trunk/packages/vim-spellfiles/debian/control.in Sat May 20 06:03:37 2006 @@ -2,7 +2,7 @@ Section: text Priority: optional Maintainer: Stefano Zacchiroli <zack@xxxxxxxxxx> -Build-Depends: debhelper (>= 4.0.0) +Build-Depends-Indep: debhelper (>= 4.0.0), aap, unzip, locales, quilt Standards-Version: 3.7.2 Package: vim-spellfiles-@CODE@ Modified: trunk/packages/vim-spellfiles/debian/copyright URL: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim-spellfiles/debian/copyright?rev=690&op=diff ============================================================================== --- trunk/packages/vim-spellfiles/debian/copyright (original) +++ trunk/packages/vim-spellfiles/debian/copyright Sat May 20 06:03:37 2006 @@ -1,13 +1,98 @@ This package was debianized by Stefano Zacchiroli <zack@xxxxxxxxxx> on Thu, 18 May 2006 23:07:06 -0500. -The dictionaries used to create spell files was downloaded from: +The recipes for downloading and building Vim spell files are part of Vim and +has been downloaded from the Vim subversion repository using the following +command: + + svn co https://svn.sourceforge.net/svnroot/vim/vim7/runtime/spell/ + +They are distributed under the term of the Vim License (which can be found at +the end of this file). http://ftp.services.openoffice.org/pub/OpenOffice.org/contrib/dictionaries -Copyright Holder: <put author(s) name and email here> - TODO put all the pairs author/licenses +TODO ADD HERE COPYRIGHT INFO ABOUT THE DICTIONARIES -License: +Copyright Holder (recipes): Bram Moolenaar <Bram@xxxxxxx> -<Put the license of the package here> +Vim License +----------- + +I) There are no restrictions on distributing unmodified copies of Vim except + that they must include this license text. You can also distribute + unmodified parts of Vim, likewise unrestricted except that they must + include this license text. You are also allowed to include executables + that you made from the unmodified Vim sources, plus your own usage + examples and Vim scripts. + +II) It is allowed to distribute a modified (or extended) version of Vim, + including executables and/or source code, when the following four + conditions are met: + 1) This license text must be included unmodified. + 2) The modified Vim must be distributed in one of the following five ways: + a) If you make changes to Vim yourself, you must clearly describe in + the distribution how to contact you. When the maintainer asks you + (in any way) for a copy of the modified Vim you distributed, you + must make your changes, including source code, available to the + maintainer without fee. The maintainer reserves the right to + include your changes in the official version of Vim. What the + maintainer will do with your changes and under what license they + will be distributed is negotiable. If there has been no negotiation + then this license, or a later version, also applies to your changes. + The current maintainer is Bram Moolenaar <Bram@xxxxxxx>. If this + changes it will be announced in appropriate places (most likely + vim.sf.net, www.vim.org and/or comp.editors). When it is completely + impossible to contact the maintainer, the obligation to send him + your changes ceases. Once the maintainer has confirmed that he has + received your changes they will not have to be sent again. + b) If you have received a modified Vim that was distributed as + mentioned under a) you are allowed to further distribute it + unmodified, as mentioned at I). If you make additional changes the + text under a) applies to those changes. + c) Provide all the changes, including source code, with every copy of + the modified Vim you distribute. This may be done in the form of a + context diff. You can choose what license to use for new code you + add. The changes and their license must not restrict others from + making their own changes to the official version of Vim. + d) When you have a modified Vim which includes changes as mentioned + under c), you can distribute it without the source code for the + changes if the following three conditions are met: + - The license that applies to the changes permits you to distribute + the changes to the Vim maintainer without fee or restriction, and + permits the Vim maintainer to include the changes in the official + version of Vim without fee or restriction. + - You keep the changes for at least three years after last + distributing the corresponding modified Vim. When the maintainer + or someone who you distributed the modified Vim to asks you (in + any way) for the changes within this period, you must make them + available to him. + - You clearly describe in the distribution how to contact you. This + contact information must remain valid for at least three years + after last distributing the corresponding modified Vim, or as long + as possible. + e) When the GNU General Public License (GPL) applies to the changes, + you can distribute the modified Vim under the GNU GPL version 2 or + any later version. + 3) A message must be added, at least in the output of the ":version" + command and in the intro screen, such that the user of the modified Vim + is able to see that it was modified. When distributing as mentioned + under 2)e) adding the message is only required for as far as this does + not conflict with the license used for the changes. + 4) The contact information as required under 2)a) and 2)d) must not be + removed or changed, except that the person himself can make + corrections. + +III) If you distribute a modified version of Vim, you are encouraged to use + the Vim license for your changes and make them available to the + maintainer, including the source code. The preferred way to do this is + by e-mail or by uploading the files to a server and e-mailing the URL. + If the number of changes is small (e.g., a modified Makefile) e-mailing a + context diff will do. The e-mail address to be used is + <maintainer@xxxxxxx> + +IV) It is not allowed to remove this license from the distribution of the Vim + sources, parts of it or from a modified version. You may use this + license for previous Vim releases instead of the license that they came + with, at your option. + Modified: trunk/packages/vim-spellfiles/debian/rules URL: http://svn.debian.org/wsvn/pkg-vim/trunk/packages/vim-spellfiles/debian/rules?rev=690&op=diff ============================================================================== --- trunk/packages/vim-spellfiles/debian/rules (original) +++ trunk/packages/vim-spellfiles/debian/rules Sat May 20 06:03:37 2006 @@ -17,6 +17,20 @@ # This target creates debian/control from debian/control.in init: perl debian/mk-deb-control.pl < debian/control.in > debian/control + +# TODO missing target 'dictionaries-recipes' +sources: sources-recipes +sources-recipes: + if [ -d upstream/spell-svn/.svn/ ]; then \ + svn update upstream/spell-svn/; \ + else \ + svn co https://svn.sourceforge.net/svnroot/vim/vim7/runtime/spell/ \ + upstream/spell-svn/; \ + fi + rm -rf upstream/vim-runtime-spell/ + svn export upstream/spell-svn/ upstream/vim-runtime-spell/ + cd upstream && \ + tar cvzf vim-runtime-spell.tar.gz vim-runtime-spell/ clean: dh_testdir

Previous Message by Thread: click to view message preview

Re: plan for spell files

On Thu, May 18, 2006 at 11:44:50PM -0500, Stefano Zacchiroli wrote: > I fear that if we want to be free we should build depend on all the > myspell-XX packages and patch aap recipes to use them. Tomorrow I will > check with the ftp masters. Correction. We can't easily depend on all the myspell-XX packages since some of the dictionaries used by aap recipes are not shipped in those packages. The solution I propose (with solves both the above issue and the non-freeness) is the following: - use as source tarballs for the vim-spellfiles source package the following: - the aap recipes took from the vim svn - all the dictionaries used by the recipes We then use as version of the package a date stamp and consider it a sort of svn snapshot. Of course we need to patch the recipes so that the dictionaries are not downloaded but used locally. Comments? -- 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. -!- signature.asc Description: Digital signature

Next Message by Thread: click to view message preview

Bug#367991: please lower the alternative priority on 'view' (and 'editor')

Package: mc Version: 1:4.6.1-2 Severity: normal Hi, on my system I've three (set of) packages providing alternatives for /usr/bin/view: nvi, vim(-*) and mcview-debian. These are their priorities: zack@aquarium:~$ update-alternatives --display view| grep ^/ /usr/bin/nview - priority 30 /usr/bin/mcview-debian - priority 100 /usr/bin/vim.basic - priority 30 /usr/bin/vim.full - priority 60 /usr/bin/vim.tiny - priority 10 [ I know from the nvi maintainer the nview will be lowered to 20 ] I found annoying that mcview-debian has the higher priority, especially because "view" was historically yet another way of running the 'vi' editor. Could you please lower the priority so that it is at least lesser than that of vim.basic. A good solution IMO would be 25. Wearing the hat of a vim maintainer: this will ensure that people installing 'mc' on top of a base system will have mc per default (since both nvi and vim-tiny are lower than it), but people installing 'vim' will have that per default, winning over 'mc'. If you prefer, being a discussion which require agreement on maintainers of several packages we can move it to debian-devel. I honestly think that the consensus will be the one outline above, but I maybe wrong. Of course a similar argument exists for the alternatives of /usr/bin/editor. Many thanks for your attention, Cheers. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Versions of packages mc depends on: ii libc6 2.3.6-7 GNU C Library: Shared libraries ii libglib2.0-0 2.10.2-2 The GLib library of C routines ii libgpmg1 1.19.6-22 General Purpose Mouse - shared lib ii libslang2 2.0.6-2 The S-Lang programming library - r mc recommends no packages. -- no debconf information