Re: RFS: witty (updated package)
OoO En cette nuit striée d'éclairs du dimanche 06 juillet 2008, vers 02:35, Pau Garcia i Quiles [EMAIL PROTECTED] disait : I've uploaded the new version (2.1.4, former was 2.1.3). Could you please check it? Hi! The package seems fine. I have uploaded it to ftp-master. Thanks! -- Choose a data representation that makes the program simple. - The Elements of Programming Style (Kernighan Plauger) pgpVN12aqIbXw.pgp Description: PGP signature
Re: RFS: xeji (updated package)
OoO En cette fin de nuit blanche du dimanche 06 juillet 2008, vers 06:31, Mauro Lizaur [EMAIL PROTECTED] disait : BTW, i couldn't get any lintian warnings about that, i'm using the v1.24.1 of lintian with the flags '-i -I', and checked a couple of times from my account and from pbuilder with sid up-to-date. In fact, i get this message: N: N: Lintian discovered an unused override entry in its database. Please N: remove it from the overrides file if it is not needed anymore. N: I: xeji source: unused-override menu-command-not-in-package Hi Mauro! You should run lintian against .changes. It will check both source (.dsc) and binary packages (.deb). Moreover, you put all overrides into source.lintian-overrides.You shouldput some of them in xeji.lintian-overrides instead. About the license, remove the part after END OF TERMS AND CONDITIONS. -- BOFH excuse #95: Pentium FDIV bug pgplpj4REegn6.pgp Description: PGP signature
License help needed (nvi 1.81.6-3)
Dear Jan, (I am cc-ing this to debian-mentors some of whom might be able to help.) I looked at your packaging at: http://www-pool.math.tu-berlin.de/~hesso/deb/nvi_1.81.6-3.dsc I agree that the copyright situation is a bit complex. Basically, Joerg has raised the question because the current debian/copyright does not clarify matters enough. I would try to create a debian/copyright which tries to clearly collate and organise all the copyright assertions in the code. We can then separately worry about interpretations and what an appropriate aggregated copyright is! (A document that will help to organise things is http://wiki.debian.org/Proposals/CopyrightFormat) For example, grep -rl LICENSE gives all the files that refer to the file LICENSE which is the BSD 3-clause license file. This reduces the number of files that one needs to examine for variations. Another example. You probably need to include the top portion of regex/COPYRIGHT in debian/copyright according what is stated there. That is the license of Henry Spencer who is the original author. Moreover, he has specifically said that *his* code is _not_ subject to any license of the Regents of the University of California! The _modifications_ to that code are under distributed under BSD-3. This is all a bit painful but I am sure that we will all thank you for this effort. I too will try to help by producing my version of debian/copyright for this package. Regards, Kapil. -- signature.asc Description: Digital signature
Re: RFS: witty (updated package)
Quoting Vincent Bernat [EMAIL PROTECTED]: OoO En cette nuit striée d'éclairs du dimanche 06 juillet 2008, vers 02:35, Pau Garcia i Quiles [EMAIL PROTECTED] disait : I've uploaded the new version (2.1.4, former was 2.1.3). Could you please check it? Hi! The package seems fine. I have uploaded it to ftp-master. Thanks! Thank you! -- Pau Garcia i Quiles http://www.elpauer.org (Due to my workload, I may need 10 days to answer) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
Hi, there is no recommended policy or factorised code for this kind of packages. It would be nice to get consistent behaviour for lenny+1, though. On Saturday 05 July 2008, Charles Plessy wrote: After insallation, the package must: - Check if apache2 is there, This is not necessary. - if yes add a link to a configuration file in /etc/apache2/conf.d You can add that file or the link unconditionally. - restart apache. A reload should be enough. Don't restart apache if it is not necessary (as it aborts active connections and may require the admin to enter ssl key passphrases, etc.). (I am also wondering if I have to ask the user wether he agrees to restart apache...) For a restart that would probably be a good idea. It would be nice though, if the restart was only done when necessary (on new installs and on upgrades if the config file changed). For a reload, I don't think you need to ask the user. PS: would the DPKG triggers be a good mechanism to deal with this apache restarting tasks? Different packages have different needs WRT to reload/restart. I don't think a trigger would be appropriate here. Cheers, Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: License help needed (nvi 1.81.6-3)
Hi Kapil, I looked at your packaging at: http://www-pool.math.tu-berlin.de/~hesso/deb/nvi_1.81.6-3.dsc I agree that the copyright situation is a bit complex. This is all a bit painful but I am sure that we will all thank you for this effort. I too will try to help by producing my version of debian/copyright for this package. I've uploaded an updated package to the above URL and also uploaded the new copyright file separately to http://www-pool.math.tu-berlin.de/~hesso/deb/nvi.copyright Short explanation: * All files that refer to LICENSE instead of including an own license statement are covered by BSD-3 and pose no problem. * The regex/ subdirectory is covered by regex/COPYRIGHT. Original author seems to be Henry Spencer, whose license text I have included as-is. Subsequent modifications are by UCB and therefore under BSD-3. * The clib/ subdirectory has BSD-4 license texts, but the only copyright holder is UCB, so due to their retroactive removal of the ad-clause I believe those to be equivalent to BSD-3. * dist/ltmain.sh is FSF code under GPL-2+. Regards, Jan signature.asc Description: Digital signature
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
Le Sun, Jul 06, 2008 at 11:02:50AM +0200, Stefan Fritsch a écrit : On Saturday 05 July 2008, Charles Plessy wrote: - restart apache. A reload should be enough. Don't restart apache if it is not necessary (as it aborts active connections and may require the admin to enter ssl key passphrases, etc.). Thanks a lot for the answer. Would something like: if [ -x /etc/init.d/apache2 ]; then if which invoke-rc.d /dev/null 21; then invoke-rc.d apache2 reload else /etc/init.d/apache2 reload fi fi be acceptable? It would be nice though, if the restart was only done when necessary (on new installs and on upgrades if the config file changed). Hmmm, I am not sure to know how to test if the config was changed... Have a nice day, -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
hello, On Sun, Jul 06, 2008 at 10:19:34PM +0900, Charles Plessy wrote: if [ -x /etc/init.d/apache2 ]; then if which invoke-rc.d /dev/null 21; then invoke-rc.d apache2 reload else /etc/init.d/apache2 reload fi fi why not something simple like /etc/init.d/apache2 reload || error_function this will work in most cases and all the tests can be done in error_function. regards -- Marc Chantreux BibLibre, expert en logiciels libres pour l'info-doc http://biblibre.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
Le Sun, Jul 06, 2008 at 03:41:09PM +0200, Marc Chantreux a écrit : On Sun, Jul 06, 2008 at 10:19:34PM +0900, Charles Plessy wrote: if [ -x /etc/init.d/apache2 ]; then if which invoke-rc.d /dev/null 21; then invoke-rc.d apache2 reload else /etc/init.d/apache2 reload fi fi why not something simple like /etc/init.d/apache2 reload || error_function Because invoking directly init.d scripts is forbidden by the Policy: http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.3.3 The package maintainer scripts must use invoke-rc.d to invoke the /etc/init.d/* initscripts, instead of calling them directly. For the test of existence of /etc/init.d/apache2, it may be a matter of taste... In that case again, having some helper functions would make the the script easier to read and factorise some code... Bonne journée -- Charles Plessy http://charles.plessy.org Wakō, Saitama, Japan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: yabause - Yet Another Buggy And Uncomplete Saturn Emulator
Hi Vincent, On Sat, 05 Jul 2008 20:25:37 +0200 Vincent Bernat wrote: OoO En cette nuit nuageuse du mercredi 02 juillet 2008, vers 00:45, Evgeni Golov [EMAIL PROTECTED] disait : yabause- Yet Another Buggy And Uncomplete Saturn Emulator yabause-gtk - Yet Another Buggy And Uncomplete Saturn Emulator - Gtk port yabause-qt - Yet Another Buggy And Uncomplete Saturn Emulator - Qt port Does free games exist? If not, you should put yabause in contrib. Moreover, a ROM seems to be needed. Maybe you should explain what is needed to run a game in README.Debian. Yes, free games exist, see my second mail, and here: http://vieille.merde.free.fr/ And no, a BIOS ROM is not needed (it may be needed for some commercial games, but usually the bios emulation of Yabause is enough). The long description is a bit short. The fact that the emulator is licensed under GNU GPL is not revelant. Mh, true. Will try to make it better. In debian/rules, there is no build target. This is a mandatory target. Ups, true, will add one, depending on build-gtk and build-qt Regards Evgeni -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: yabause - Yet Another Buggy And Uncomplete Saturn Emulator
OoO Vers la fin de l'après-midi du dimanche 06 juillet 2008, vers 16:42, Evgeni Golov [EMAIL PROTECTED] disait : Does free games exist? If not, you should put yabause in contrib. Moreover, a ROM seems to be needed. Maybe you should explain what is needed to run a game in README.Debian. Yes, free games exist, see my second mail, and here: http://vieille.merde.free.fr/ And no, a BIOS ROM is not needed (it may be needed for some commercial games, but usually the bios emulation of Yabause is enough). You should mention it in README.Debian. ftp-master will ask the same questions, I think. -- je ne parle pas de secte moi, je parle d'extraterrestres et de religions. -+- Ant1 in Guide du neuneu Usenet : David Vincent les a vus -+- pgpiTKXiGb2NE.pgp Description: PGP signature
Re: RFS: mpop - POP3 mail retriever (updated version)
Carlos Martín Nieto [EMAIL PROTECTED] (05/07/2008): My usual sponsor is unavailable, so I'm asking here for someone to sponsor this upload for me. Hi, I'm going to have a look in a few hours unless someone beats me to it. Mraw, KiBi. signature.asc Description: Digital signature
Re: License help needed (nvi 1.81.6-3)
Dear Jan, On Sun, 06 Jul 2008, Jan Christoph Nordholz wrote: I've uploaded an updated package to the above URL and also uploaded the new copyright file separately to http://www-pool.math.tu-berlin.de/~hesso/deb/nvi.copyright Short explanation: * All files that refer to LICENSE instead of including an own license statement are covered by BSD-3 and pose no problem. * The regex/ subdirectory is covered by regex/COPYRIGHT. Original author seems to be Henry Spencer, whose license text I have included as-is. Subsequent modifications are by UCB and therefore under BSD-3. * The clib/ subdirectory has BSD-4 license texts, but the only copyright holder is UCB, so due to their retroactive removal of the ad-clause I believe those to be equivalent to BSD-3. * dist/ltmain.sh is FSF code under GPL-2+. This is more or less what I thought as well. Some points: a. dist/ltmain.sh is a generated file and so I think it need not be described in debian/copyright separately. That file says: # As a special exception to the GNU General Public License, if you # distribute this file as part of a program that contains a # configuration script generated by Autoconf, you may include it under # the same distribution terms that you use for the rest of that program. b. While I concur with you on the clib/ directory, I think it would be good if we get a second opinion (perhaps Joerg's?) from debian-mentors. Alternatively/additionally, the statement you made above should probably be made in debian/copyright so that it is clear on what basis we are drawing our conclusions. This is because the files explicitly contain the BSD-4 clause license. c. The debian/copyright file in the URL above makes no mention of the debian packaging. That is copyrighted by the maintainer(s) and a license has to be specified. Regards, Kapil. -- signature.asc Description: Digital signature
Re: License help needed (nvi 1.81.6-3)
Hi, This is more or less what I thought as well. Some points: all points fixed, package updated. There were no license statements in the package when I took over, and I've re-done most of the packaging for 1.81.6 from scratch anyway, so I've just entered myself as holder for debian/* (or is it common practice to try to reach all previous maintainers?). Regards, Jan signature.asc Description: Digital signature
Re: RFS: mozvoikko - Finnish spell-checker extension for Iceweasel and Icedove
Thanks for your help.
I uploaded new version to mentors.debian.net:
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=mozvoikko
2008/7/4 Mike Hommey [EMAIL PROTECTED]:
On Thu, Jul 03, 2008 at 07:06:21PM +0300, Heikki Mäntysaari wrote:
I do mean /usr/share/mozilla/extensions. /usr/share/mozilla-extensions
is where I did put these shared files in my mozilla extensions packages,
and where symlinks in /usr/lib/$app/extensions point to.
/usr/share/mozilla/extensions is a new location that new upstream looks at.
That means iceweasel 3.0 does look into /usr/share/mozilla/extensions
too, and doesn't need a link in /usr/lib/iceweasel/extensions if the
shared files are in /usr/share/mozilla/extensions. It also means iceape
2 and icedove 3, when they will be available, will also look there.
Note that directory names in /usr/share/mozilla/extensions must contain
a '@' character (usually, that would be [EMAIL PROTECTED]) or be a
uuid between curly braces ({}).
Mike
--
-Heikki Mäntysaari
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: projectcenter.app (updated package)
Dear mentors, I am looking for a sponsor for the new version 0.5.0~20080704-1 of my package projectcenter.app. It builds these binary packages: projectcenter.app - IDE for GNUstep Development The package appears to be lintian clean. The upload would fix these bugs: 443666, 443676, 451460, 453429, 471755 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/p/projectcenter.app - Source repository: deb-src http://mentors.debian.net/debian unstable main - dget http://mentors.debian.net/debian/pool/main/p/projectcenter.app/projectcenter.app_0.5.0~20080704-1.dsc I would be glad if someone uploaded this package for me. (The package has been buggy and unusable since quite some time -- this upload would fix all bugs and all lintian errors/warnings.) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: mozvoikko - Finnish spell-checker extension for Iceweasel and Icedove
On Sun, Jul 06, 2008 at 07:50:23PM +0300, Heikki Mäntysaari wrote: Thanks for your help. I uploaded new version to mentors.debian.net: http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=mozvoikko I only took a quick look but here is what I have to say: - Don't depend on icedove 3, it won't be in the archive for months - You really don't need to put a link in /usr/lib/iceweasel/extensions, since you are depending on iceweasel 3, and this version will look into /usr/share/mozilla/extensions. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
Stefan Fritsch [EMAIL PROTECTED] writes: On Saturday 05 July 2008, Charles Plessy wrote: - if yes add a link to a configuration file in /etc/apache2/conf.d You can add that file or the link unconditionally. That would really upset me if I were a systems administrator. Most of my Apache configurations have multiple virtual hosts, and having some package randomly add itself to the namespace of every virtual host I run, possibly taking over pages that were currently serving some other purpose, would be extremely annoying. I'd want at least a debconf prompt before something added itself to the global Apache configuration. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: License help needed (nvi 1.81.6-3)
Kapil Hari Paranjape [EMAIL PROTECTED] writes: a. dist/ltmain.sh is a generated file and so I think it need not be described in debian/copyright separately. That file says: # As a special exception to the GNU General Public License, if you # distribute this file as part of a program that contains a # configuration script generated by Autoconf, you may include it under # the same distribution terms that you use for the rest of that program. People generally don't mention the Autotools files in debian/copyright, but I think that's more a matter of convenience and because they have well-known and non-problematic licenses. Since we're distributing them, to be fully and formally correct, we should probably document the license status. (Not that I expect many people to go to the effort, but I do do so when I have time for my packages.) -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Re: RFS: bluemindo
Hi, well, you've done it in an overcomplicated way. You call dh_link manually, but thats not neccessary as CDBS already calls it. You just have to add a file debian/links containing all the links that you need to create. This also saves some build-time (not that many, but consider 1000 packages calling a perl script like dh_link twice for no reason), what I consider quiet important, as some architectures are already overloaded. I've moved it to debian/links (and debian/install for the dh_install call). I also modified the debian/copyright file, it should be a little cleaner, and it now includes the PSF license. Given that it isn't a 'install' step you should move it to another target. The CDBS documentation has 'build/foo' for it. Done. I've added how to disable patches in README.source It seems to be the only way with simple-patchsys. [...] Yeah, alright. [...] Great. [...] Perfect. [...] Okay, good. Thanks :) - The enumeration in the description is confusing. I still think that this is true and I would also prefer a more terse description. Bluemindo is a really simple but powerful audio player in Python/PyGTK, using GStreamer. . Features include: * Download pictures for artists and album or lyrics of the current playing song * Different view modes (lightweight, basic, normal or full) * Plugin support * Desktop notifications * Change the status message of the Gajim Instant Messenger * Send music to your last.fm profile or your Jabber account I think its not adequate to over-detailled describe the feature (like the details of the view modes). Thats what documentation is for. The user just needs a chance to decide weither this player is worth beeing tried out. I'm open for discussion if the 3 items that are featured via plugins should be handled seperately, but I'm arguing that they are part of the package distribution so this is eventually not needed. I replaced the description with yours and I added notes about optional dependencies. About the code duplication thing: If I do search for example for audioscrobbler.py with apt-file, then I do find 4 or 5 different copies of this file. Even if upstream makes changes to this file (which is bad and you should teach him not to do so) it is still a code duplication and probably needs security support. So your best bet is to inform the security team, latest once the package gets accepted in the archive. Hm... Ok, I will do so. Regards, Thibaut GIRKA. signature.asc Description: Ceci est une partie de message numériquement signée
Re: Problem with implicit rule for .o files and overriding of CXXFLAGS.
At Sun, 29 Jun 2008 20:03:51 +0900,
Charles Plessy wrote:
I don't know; this text still makes me feel uneasy.
how about :
When a Debian binary package is built, environment variables such as
{{{CFLAGS}}} and {{{CXXFLAGS}}} are set by {{{dpkg-buildpackage}}}
and may override the corresponding variables in the
{{{Makefile}}}.
Much better, but it doesn't happen with `proda' (namely because
CXXFLAGS is defined there) and perhaps lots of other packages:
$ export CXXFLAGS=-Wextra -Werror -O3
$ make
g++ -g -W -Wall -pedantic -DVERSION=\1.00\ -c -o AlignedFragment.o
AlignedFragment.cc
[...]
For the typical autoconfiscated package, variables as set by
`dpkg-buildpackage' will propagate, since ./configure will pick them
up from the environment.
But... many packages already define conditionally at least
CFLAGS/CXXFLAGS in debian/rules to cater for `noopt' (and `nostrip'
when not handled automatically by `dh_strip'). For LDGFLAGS, many
packages pass `-Wl,--as-needed' at least. So it is wrong to rely on
dpkg-buildpackage for doing the right thing (which partly explains why
only 20-40 RC bugs popped up when this functionality was introduced)
-- the maintainer must be aware of this behaviour, but it is far from
sufficient to ensure that the package in question is policy compliant.
The matter is more complex in general; add here the well known fact
that a truckload of upstream makefiles/build systems is broken.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: projectcenter.app (updated package)
OoO Pendant le repas du dimanche 06 juillet 2008, vers 19:11, Yavor Doganov [EMAIL PROTECTED] disait : I am looking for a sponsor for the new version 0.5.0~20080704-1 of my package projectcenter.app. It builds these binary packages: projectcenter.app - IDE for GNUstep Development Hi Yavor! Maybe you should also ask Debian GNUstep maintainers. -- Test programs at their boundary values. - The Elements of Programming Style (Kernighan Plauger) pgp8ZHAR4mF2Z.pgp Description: PGP signature
Re: Factorised code for adding a file in /etc/apache2/conf.d/ and restarting apache ?
OoO Pendant le journal télévisé du dimanche 06 juillet 2008, vers 20:05, Russ Allbery [EMAIL PROTECTED] disait : - if yes add a link to a configuration file in /etc/apache2/conf.d You can add that file or the link unconditionally. That would really upset me if I were a systems administrator. Most of my Apache configurations have multiple virtual hosts, and having some package randomly add itself to the namespace of every virtual host I run, possibly taking over pages that were currently serving some other purpose, would be extremely annoying. I'd want at least a debconf prompt before something added itself to the global Apache configuration. It seems to be best practice to not add anything that could disrupt a running Apache configuration. For example, aliases are left commented while Directory directives are uncommented. -- prom_printf(Detected PenguinPages, getting out of here.\n); 2.0.38 /usr/src/linux/arch/sparc/mm/srmmu.c pgpYLo0zLmrEw.pgp Description: PGP signature
Re: RFS: projectcenter.app (updated package)
Vincent Bernat wrote: Maybe you should also ask Debian GNUstep maintainers. I am one of them (I believe so, at least :-)), and Hubert Chathi (uhoreg) -- the only DD in the team -- just uploaded this particular package (thanks!). I'm just trying to find a permanent sponsor, as Hubert cannot possibly upload every GNUstep stuff out there. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: libzendframework-php
Dear mentors, I am looking for a sponsor for my package libzendframework-php. Package name: libzendframework-php Version : 1.5.2-1 Upstream Author : Zend Technologies USA, Inc URL : http://framework.zend.com/ License : BSD Section: web It builds these package: libzendframework-php - High quality framework for Web Development Description: Zend Framework is a high quality framework for developing Web Applications and Web Services with PHP. It provides solutions for building modern, robust, and secure websites The package appears to be lintian clean. The upload would fix these bugs: 428760 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/l/libzendframework-php - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/l/libzendframework-php/libzendframework-php_1.5.2-1.dsc I would be glad if someone uploaded this package for me. Kind regards Andrea Giardina -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Andrea Giardina wrote: ... http://mentors.debian.net/debian/pool/main/l/libzendframework-php/libzendframework-php_1.5.2-1.dsc I would be glad if someone uploaded this package for me. If it had been so simple I'd have uploaded the package several months ago. Please don't use such generic packaging and actually read what I already wrote. Kind regards Andrea Giardina -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Andrea Giardina [EMAIL PROTECTED] writes: It builds these package: libzendframework-php - High quality framework for Web Development Please note the best packaging practice for the package synopsis URL:http://www.debian.org/doc/developers-reference/ch-best-pkging-practices#s-bpp-pkg-synopsis. The synopsis should *not* be capitalised like a full sentence. Description: Zend Framework is a high quality framework for developing Web Applications and Web Services with PHP. It provides solutions for building modern, robust, and secure websites Please separate paragraphs with a blank line, which is achieved with a full stop (.) on a line by itself. Also, terminate full sentences with a full stop. The terms web applications and web services are not proper nouns (i.e. they're not names of specific entities), so should not be capitalised. Hence: Description: high quality framework for Web Development Zend Framework is a high quality framework for developing web applications and web services with PHP. . It provides solutions for building modern, robust, and secure websites. -- \ “I have no race prejudices nor caste prejudices nor creed | `\prejudices. All I care to know is that a man is a human being, | _o__) and that is enough for me; he can't be any worse.” —Mark Twain | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS: libzendframework-php
Ben Finney [EMAIL PROTECTED] writes: The terms web applications and web services are not proper nouns (i.e. they're not names of specific entities), so should not be capitalised. Hence: Description: high quality framework for Web Development Following my own advice, that should be: Description: high quality framework for web development -- \ “It's a good thing we have gravity or else when birds died | `\ they'd just stay right up there. Hunters would be all | _o__)confused.” —Steven Wright | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
