Thread: COPYING.txt in Debian package
Cream is a free, easy-to-use configuration of the Vim text editor
Brought to you by:
digitect
From: Christoph H. <em...@ch...> - 2004-07-06 22:23:06
|
Hi, Steve et al... When running the menu item 'Help' / 'About Cream' / 'License' the file COPYING.txt will usually be displayed. Due to the nature of the Debian policy documentation files belong into /usr/share/doc/cream/... Could you think of a way to override the location of the license text file? In the cream-user.vim perhaps? Christoph -- ~ ~ ".signature" [Modified] 3 lines --100%-- 3,41 All |
From: Steve H. <dig...@mi...> - 2004-07-07 01:45:49
|
On Tue, 2004-07-06 at 18:22, Christoph Haas wrote: > Hi, Steve et al... > > When running the menu item 'Help' / 'About Cream' / 'License' the > file COPYING.txt will usually be displayed. Due to the nature of the > Debian policy documentation files belong into > /usr/share/doc/cream/... Does this apply to files like COPYING, INSTALLATION, CHANGELOG, TODO, and README, too? I am perplexed that these file are not near the scripts themselves, FSF once specifically asked that we do this. Both docs/ and docs-html/ are really nothing more than glorified versions of the ancient FSF-standard accompanying docs. > Could you think of a way to override the location of the license > text file? In the cream-user.vim perhaps? One way would be to look for it in $CREAM/docs/ and if not found, simply post a link to Cream's web page. (Or GPL's for that matter.) [epiphany] It would be smart for someone to standardize License installation the way applications are installed. You could have GPL1, GPL2, BSD-ads, BSD-noads, AllYourBaseAreBelongToUs, etc., installed once and apps could reference them rather than having them copied 150 times. There could even be a dependancy tree so that certain apps couldn't be installed if there were license conflicts. I tell ya, they don't pay me enough. -- Steve Hall [ dig...@mi... ] Cream... the Vim text editor in sheep's clothing! http://cream.sourceforge.net |
From: Christoph H. <em...@ch...> - 2004-07-07 17:01:48
|
On Tue, Jul 06, 2004 at 09:49:51PM -0400, Steve Hall wrote: > On Tue, 2004-07-06 at 18:22, Christoph Haas wrote: > > When running the menu item 'Help' / 'About Cream' / 'License' the > > file COPYING.txt will usually be displayed. Due to the nature of the > > Debian policy documentation files belong into > > /usr/share/doc/cream/... > > Does this apply to files like COPYING, INSTALLATION, CHANGELOG, TODO, > and README, too? Not really. Unless they are directly accessed from the running vim. > I am perplexed that these file are not near the scripts themselves, > FSF once specifically asked that we do this. Both docs/ and docs-html/ > are really nothing more than glorified versions of the ancient > FSF-standard accompanying docs. Interesting though confusing. I'm not a policy God. Debian's policy just defines a single place where all documentation has to go to. So users wouldn't need to search the whole system for pieces of information. [epiphany removed for the sake of the faint-hearted readers] To not make you bother about such distribution details I think I will move the documentation files to /usr/share/doc/cream/... but create a symlink so cream can still find its files. That should do it. I can't expect you to implement a kind of artificial intelligence just because long-bearded ugly package maintainers have fun ripping the files apart. :) Christoph -- ~ ~ ".signature" [Modified] 3 lines --100%-- 3,41 All |
From: Steve H. <dig...@mi...> - 2004-07-08 01:49:15
|
On Wed, 2004-07-07 at 13:01, Christoph Haas wrote: > On Tue, Jul 06, 2004 at 09:49:51PM -0400, Steve Hall wrote: > > On Tue, 2004-07-06 at 18:22, Christoph Haas wrote: > > > When running the menu item 'Help' / 'About Cream' / 'License' > > > the file COPYING.txt will usually be displayed. Due to the > > > nature of the Debian policy documentation files belong into > > > /usr/share/doc/cream/... > > > > Does this apply to files like COPYING, INSTALLATION, CHANGELOG, > > TODO, and README, too? > > Not really. Unless they are directly accessed from the running vim. Ah, so that's the distinction. Informative. > To not make you bother about such distribution details I think I > will move the documentation files to /usr/share/doc/cream/... but > create a symlink so cream can still find its files. That should do > it. Good idea. Thanks for your efforts in packaging, I (and hopefully Debian Cream users) appreciate it. > I can't expect you to implement a kind of artificial intelligence > just because long-bearded ugly package maintainers have fun ripping > the files apart. :) I suppose there's logic to it. I certainly can't claim to be any better looking, although I would take awards for shorter hair. -- Steve Hall [ dig...@mi... ] Cream... the Vim text editor in sheep's clothing! http://cream.sourceforge.net |