November 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] openSUSE GNOME & KDE Packaging Day: Nov 30 - Dec 1
by Michael Wolf 16 Nov '07

16 Nov '07

Hello Members of the openSUSE GNOME and KDE teams will be holding a packaging day (two days, actually :)). If you're interested in learning how to build KDE or GNOME packages for openSUSE, read on: http://en.opensuse.org/Packaging/Packaging_Day Michael --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

Re: [opensuse-packaging] How to deal with Python .pyc and .pyo files?
by Jan Matejek 16 Nov '07

16 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Johannes Meixner napsal(a): > Hello, > > On Nov 14 16:00 Marcus Rueckert wrote (shortened): > >>> On Wed, 2007-11-14 at 15:08 +0100, Johannes Meixner wrote: >>>> Hello, >>>> >>>> what is the recommended way for packaging Python stuff? >>>> >>>> Either >>>> have byte-compiled Python .pyc and .pyo files packaged into the RPM >>>> or >>>> let this be done by the currently actually installed Python system >>>> during run-time on the end-user's computer and not by whatever >>>> (perhaps different) Python system during package build-time? >> as we build with the same python version as the user will run it later. >> you can safely package the .pyc files. > > I understand that it is the same Python version directly after > a new system installation. > > But what happens when the user later change/update his Pyhon? > > Think about the "worst case" when the user replaces our Pyhon > with whatever self-compiled Pyhon. > > Are byte-compiled Python .pyc and .pyo files the same for any Python > and/or is any Python sufficiently smart to know when .pyc and/or .pyo > files are outdated (even if the matching .py files are unchanged)? They are (mostly) the same, AND there is some kind of version check in the file. Don't worry about this, python would notice any problem by itself ;e) Second worst case would be if you upgraded to a new major version of python, i.e. from 1.5 to 2.0. In that case python would report errors about bad bytecode, and i'm really not sure if it would recompile automatically. But i think it would. Worst case would be if you downgraded, i don't think python 1.5 could cope... But on the other hand, i don't think this problem is worth considering. That's why python has versioned site-packages. In your other post you noticed that python files are strewn all over the system. In most cases that is bad packaging. Generally speaking, all python files should be located in /usr/lib[64]/pythonx.y/site-packages (of course there are exceptions, but let's not go into that). >> i would even recommend packaging >> them so they get removed if you uninstall the package. > > Removal when uninstalling could also be done by whatever > other magic (e.g. via %ghost or a %preun scriptlet in RPM). Bad magic, bad bad magic. We have enough trouble with scriptlets as they are now. > I wonder why in this case small RPMs seem not to count. > > For example the installed .pyc and .pyo files in python > on a openSUSE 10.3 i386 system are more than 7MB and > still about 1.6MB after "bzip2" so that those files > should make the python RPM about 1.6MB bigger. > > At least according to > http://www.python.org/doc/1.5.1p1/tut/node43.html > I wonder if there is a noticeable advantage to provide > .pyc and .pyo files in the RPM because it reads: > "A program doesn't run any faster when it is read from > a ".pyc" or ".pyo" file than when it is read from a ".py" file; > the only thing that's faster about ".pyc" or ".pyo" files is > the speed with which they are loaded." True, and that's why we provide them. Think about it this way: python programs need to be compiled too. We provide the "binaries" form so that users' computers don't need to do the compilation themselves. But even more important is that regular user doesn't have write access to wherever the .py files are stored. You would need to run each python program as root first, otherwise python would need to compile the sources every time the program is run. > I am no Python expert at all and I would be happy if a Python expert > could provide some background information. is this background sufficient? ;e) > > > Kind Regards > Johannes Meixner regards jan matejek -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHPJmGjBrWA+AvBr8RAu4nAJ44givXOzCG9LY1ge9DWoSouwTFHQCgjlf2 WA9ogJSDXliAvm2NxmAsy2E= =zapY -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 2

[opensuse-packaging] How to deal with Python .pyc and .pyo files?
by Johannes Meixner 15 Nov '07

15 Nov '07

Hello, what is the recommended way for packaging Python stuff? Either have byte-compiled Python .pyc and .pyo files packaged into the RPM or let this be done by the currently actually installed Python system during run-time on the end-user's computer and not by whatever (perhaps different) Python system during package build-time? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 7

[opensuse-packaging] KMP package file
by Alex Lau 13 Nov '07

13 Nov '07

Dear all packagers Let say we wanted to put document into the kmp is that possible and is it against police? Thanks Alex ----------------------------------- 刘俊贤 Alex Lau PRC Beijing Linux R&D Engineer Mainland-Mobile (8610) 13910181404 HongKong-Mobile (852) 91621631 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 2

[opensuse-packaging] libdbcxx_cxx-4_5-devel missing on 10.3 and Factory
by Pascal Bleser 13 Nov '07

13 Nov '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Trying to build an application that includes "db_cxx.h". On 10.2 and below, that file is part of "db-devel" but on 10.3 it has been split out into libdb_cxx-*-devel Problem is, it has: * libdb_cxx-4_4-4.4.20-28.i586.rpm * libdb_cxx-4_4-devel-4.4.20-28.i586.rpm but it also has: * libdb-4_5-devel-4.5.20-29.i586.rpm * libdb-4_4-devel-4.4.20-28.i586.rpm When the OBS starts the build VM for 10.3 and Factory, it preinstalls libdb-4_5: preinstalling libdb-4_5... My .spec file includes %if %suse_version >= 1030 BuildRequires: libdb_cxx-4_4-devel %endif which causes this: installing libdb-4_4-devel-4.4.20-28 installing libdb-4_5-devel-4.5.20-29 file /usr/include/db.h from install of libdb-4_5-devel-4.5.20-29 conflicts with file from package libdb-4_4-devel-4.4.20-28 Makes sense but... where's libdb_cxx-4_5-devel ? cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHOVyJr3NMWliFcXcRAvQAAJ46LrZ+FCYYdL8TENjhFHvR2IEiGQCeKd9i X60m9Fn9S5wZpiXNRjVM30M= =NSZn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

2 1

[opensuse-packaging] python and valgrind
by Martin Vidner 12 Nov '07

12 Nov '07

Hi, when hunting a bug in yast2-python-bindings I tried to use valgrind on python. How silly of me! Errors from inside python all over the place: mvidner@valkyrie:~$ valgrind python -c "print 'hello'" 2>&1 | wc -l 558 I am attaching a suppression file to fix that. Can't python use more civilized code? Apparently not, as explained in http://svn.python.org/projects/python/trunk/Misc/README.valgrind Can valgrind include this suppression by default? mvidner@valkyrie:~$ valgrind --suppressions=PyObject_Free-sucks.supp python -c "print 'hello'" 2>&1 | wc -l 23 -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu

1 0

[opensuse-packaging] dependencies, why and where
by Christofer Olofsson 12 Nov '07

12 Nov '07

Hi everyone, hope i'm on the correct list. Let me start by thanking you for opensuse, not to come off to bad asking these questions ;) Why does a package depend on another and where/how can I find out how? I'm asking this because there are certain deps. that I don't fully understand; Such as php5 depends sqlite, php5-json and other packages that I atleast, cannot find out why it does? And man, installs cronjob which would use makewhatis, but does not depend on it? subversion.. want's apache but not any DAV support? I'm puzzled, please enlighten me =) ps. I really love that the base install is below 400MB, thank you for that! ;) c. -- When mirror toward umbrella ruminates, diskette for prays. -------------------------------------------------------- Christofer Olofsson Technical Specialist Net Entertainment NE AB, Birger Jarlsgatan 57 B, S-113 56 Stockholm, Sweden T: , F:+46 8 556 967 07 christofer.olofsson(a)netent.com, www.netent.com Better Games --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 7

[opensuse-packaging] openSUSE Factory update (gcc 4.3)
by Adrian Schröter 12 Nov '07

12 Nov '07

Hi, the openSUSE:Factory distro got an update and does use gcc 4.3 from now on as default compiler. This may have some effect when compiling your stuff inside or outside of the build service. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian(a)suse.de --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Procinfo-NG 2.0.135 released.
by tabris 11 Nov '07

11 Nov '07

Changelog * Various packaging changes, at request of OpenSuSE project. * Silence some sprintf warnings about %llu vs %lu and 64-bit vs 32-bit arches. * Move bzero macro into routines.cpp * Add C++ type-safe zalloc macro * move readFile into routines.cpp * Make readFile accept larger lines (40958 bytes instead of 4094 bytes). ** Probably should be made adaptive, rather than using a static-sized buffer * Cygwin support. ** IRQ stats don't exist ** Disk stats don't exist ** 'nice' CPU stat doesn't work, always zero. * Reorganize a lot of code ** prettyPrint is now in its own independent .cpp file ** Various time-routine bugfixes ** Added some time-specific macro/constants, to make people happy who hate magic numbers. * Add __time_rel_long from SrSv, not that I use it in this project.

1 0

[opensuse-packaging] -mini packages purpose
by Cristian Rodriguez 09 Nov '07

09 Nov '07

Hi: What is the specific reason for having foobar-mini packages ? I guess those provides less functionality but for what use cases are needed or what is the rationale behind them ? -- "If eval() is the answer, you're almost certainly asking the wrong question." --Rasmus Lerdorf Cristian Rodríguez R, Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/ --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 7