[opensuse-packaging] new package: python-psycopg2
I have in my home:jnelson-suse project a ready-to-go package: python-psycopg2 I'd like to get it in to Factory, but the first step is to use submitreq. I'm not sure which devel project to submit it to, however, therefore I would like some suggestions, please! -- Jon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
On Mon, Aug 24, 2009 at 09:13:41AM -0500, Jon Nelson wrote:
I have in my home:jnelson-suse project a ready-to-go package: python-psycopg2 I'd like to get it in to Factory, but the first step is to use submitreq. I'm not sure which devel project to submit it to, however, therefore I would like some suggestions, please!
devel:languages:python is the most likely choice. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Ok. I created a request (in devel:languages:python) but I think I did it wrong. Request 18573. Regarding what I wanted to add to the request: The upstream project is years old. it is the de-facto mechanism by which python programs access postgresql. It is well maintained and active. I use it every day, in one form or another, and it's remarkably stable. It does not have a track record of security issues that I am aware of. The license is GPL w/exception or ZPL (Zope Public License). I'm including the complete LICENSE file below - everything betweeen the ____LICENSE____ "quotes". ____LICENSE____ psycopg and the GPL =================== psycopg is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. See file COPYING for details. As a special exception, specific permission is granted for the GPLed code in this distribition to be linked to OpenSSL and PostgreSQL libpq without invoking GPL clause 2(b). Note that the GPL was chosen to avoid proprietary adapters based on psycopg code. Using psycopg in a proprietary product (even bundling psycopg with the proprietary product) is fine as long as: 1. psycopg is called from Python only using only the provided API (i.e., no linking with C code and no C modules based on it); and 2. all the other points of the GPL are respected (you offer a copy of psycopg's source code, and so on.) Alternative licenses ==================== If you prefer you can use the Zope Database Adapter ZPsycopgDA (i.e., every file inside the ZPsycopgDA directory) user the ZPL license as published on the Zope web site, http://www.zope.org/Resources/ZPL. Also, the following BSD-like license applies (at your option) to the files following the pattern psycopg/adapter*.{h,c} and psycopg/microprotocol*.{h,c}: Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions: 1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. 2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. 3. This notice may not be removed or altered from any source distribution. psycopg is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. Proprietary licenses ==================== A non-exclusive license is available for companies that want to include psycopg in their proprietary products without respecting the spirit of the GPL. The price of the license is one day of development done by the author, at the consulting fee he applies to his usual customers at the day of the request. ____LICENSE____ -- Jon -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org
Hi, On Mon, Aug 24, 2009 at 09:26:32AM -0500, Jon Nelson wrote:
Ok. I created a request (in devel:languages:python) but I think I did it wrong. Request 18573.
The python-psycopg2 package is already in devel:languages:python (was there before you sent the request). However, the package in devel:languages:python is broken and also older than the package in your project. So I think you should: 0) revoke request #18573 1) branch the package from devel:languages:python 2) update it and fix it 3) submit request This way the package history won't be lost. For details, take a look at [1]. Regarding getting the package to Factory, it should be done after 11.2 is out since Factory is now frozen. [1] http://en.opensuse.org/Build_Service/Collaboration HTH -- Best regards / s pozdravem Petr Uzel, openSUSE Community Multiplier Team ----------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: puzel@suse.cz Lihovarská 1060/12 http://www.suse.cz 190 00 Prague 9, CR
participants (3)
-
Jon Nelson
-
Marcus Meissner
-
Petr Uzel