openSUSE Packaging October 2011

packaging@lists.opensuse.org

34 participants
28 discussions

[opensuse-packaging] Desktop-related macros for scriptlets

by Vincent Untz

Hi, Something I probably failed to document properly in 11.4 is the new macros that got introduced for desktop-related things (some of them being, arguably, GTK+-only). They were introduced to fix various issues, and move away from the SuSEconfig scripts. With rpm 4.9, we might be able to use another solution. In that case, the macros listed below will just expand to an empty string and do nothing. So it won't harm to use them either. Desktop-related macros ====================== a) Package installs a .desktop file in /usr/share/applications Macros: %desktop_database_post/%desktop_database_postun What it does: calls update-desktop-database to update a cache mapping MIME types to apps handling them. This is needed to make the desktops aware that an app can handle a MIME type. b) Package installs a MIME definition (in /usr/share/mime): Macros: %mime_database_post/%mime_database_postun What it does: calls update-mime-database to update the database containing information about all MIME definitions. c) Package installs an icon in hicolor (/usr/share/icons/hicolor): Macros: %icon_theme_cache_post/%icon_theme_cache_postun What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for hicolor, as specified by the spec. This is needed to make the icon visible to GTK+ apps. d) Package installs an icon in another icon theme (let's say "geeko" theme, /usr/share/icons/geeko) Macros: %icon_theme_cache_post geeko / %icon_theme_cache_postun geeko What it does: calls gtk-update-icon-cache (if existing) to update the GTK+ icon cache for geeko. This is needed to make the icon visible to GTK+ apps. e) Package installs a GSettings schema (in /usr/share/glib-2.0/schemas): Macros: %glib2_gsettings_schema_post/%glib2_gsettings_schema_postun %glib2_gsettings_schema_requires (similar to %py_requires) What it does: calls glib-compile-schemas to build the blob containing the data for all schemas. This is needed to have your app not crash :-) f) Package installs a gio module (in /usr/lib/gio/modules): Macros: %glib2_gio_module_post/%glib2_gio_module_postun %glib2_gio_module_requires (similar to %py_requires) What it does: calls gio-querymodules to update a cache listing all gio modules and the extension points they are using. This is needed to make the gio module known to gio. g) Package installs a gdk-pixbuf loader (in /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders): Macros: %gdk_pixbuf_loader_post/%gdk_pixbuf_loader_postun %gdk_pixbuf_loader_requires (similar to %py_requires) What it does: calls gdk-pixbuf-query-loaders to update a cache listing all gdk-pixbuf loaders and their abilities. This is needed to make the gdk-pixbuf loader known to gdk-pixbuf. h) Package installs a GTK+ (2 or 3) IM module (in /usr/lib/gtk-2.0/2.10.0/immodules or /usr/lib/gtk-3.0/3.0.0/immodules): Macros: %gtk2_immodule_post/%gtk2_immodule_postun %gtk2_immodule_requires %gtk3_immodule_post/%gtk3_immodule_postun %gtk3_immodule_requires What it does: calls gtk-query-immodules-2.0/gtk-query-immodules-3.0 to build a cache listing all IM modules and the locale/language they apply to. You obviously need to only call the gtk2/gtk3 version, depending on which version of GTK+ you target. This is needed to make the IM module known to GTK+. i) Package installs a pango module (in /usr/lib/pango/1.6.0/modules): Macros: %pango_module_post/%pango_module_postun %pango_module_requires (similar to %py_requires) What it does: calls pango-querymodules to update a cache listing all pango modules and information about what they handle. This is needed to make the module known to pango. Thanks, Vincent -- Les gens heureux ne sont pas pressés. -- Les gens heureux ne sont pas pressés. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 years, 6 months

[opensuse-packaging] cups: upgrade from 1.4.x to version 1.5.0

by Johannes Meixner

Hello, in the OBS project "Printing" there is now CUPS version 1.5.0 for various openSUSE and SLE versions. It may take a few hours until RPMs appear under http://download.opensuse.org/repositories/Printing/ For openSUSE:Factory there is submitrequest 86888 pending to upgrade CUPS in openSUSE:Factory to version 1.5.0. See https://bugzilla.novell.com/show_bug.cgi?id=722057 for background information. Basically: According to http://www.cups.org/roadmap.php CUPS 1.4.x is no longer maintained by upstream which is the reason to upgrade to version 1.5.0. Backward incompatible changes: * The main header cups/cups.h no longer includes the PPD header cups/ppd.h which may require code changes to applications. * CUPS no longer supports the old ~/.cupsrc or ~/.lpoptions files from CUPS 1.1.x. The ~/.cups/client.conf and ~/.cups/lpoptions files that were introduced in CUPS 1.2 must now be used. * The scheduler now requires that filters and backends have group write permissions disabled (security). This means: Compiling software which use the CUPS PPD API but do not explicitly include the <cups/ppd.h> header file would fail. This backward-incompatible change should show up during package build in OBS so that affected packages can be fixed. In old-style applications which still use ~/.cupsrc and ~/.lpoptions user default settings would no longer work. I have no idea how many such old-style applications may exits. Printer driver packages which install their own filters and backends with group write permissions would no longer work. I will check those packages in OBS. For third party printer drivers from manufacturers I cannot do anything (they may no longer work without manual adjustment). I appreciate any testing and feedback regarding CUPS 1.5.0. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] KDE3 pattern

by Ilya Chernykh

Hi, Stephan! I know you had some points against creating a new pattern for KDE3, especially concerning the pattern's name. But the users seem to complain about that installing KDE3 without pattern is difficult: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta… Also it seems installing not fully complete set of packages may lead the users to believe that something is broken or incomplete (like in the linked case where the user thought kde3-ksnapshot was not included in Factory while actually it belongs to kdegraphics3). I have created a bugreport concerning the KDE3 pattern with a package list: https://bugzilla.novell.com/show_bug.cgi?id=721640 I hope you can revisit the issue before the release date. The name of the pattern is not that important actually, I just hope it would not confuse the users. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] Package boinc-client for sale

by Sascha Manns

Hello mates, sadly i haven't enough time to provide future update and versions of boinc-client. ATM it is placed there: https://build.opensuse.org/package/show?package=boinc-client&project=network We have open Bugs in Bugzilla: https://bugzilla.novell.com/show_bug.cgi?id=566289 https://bugzilla.novell.com/show_bug.cgi?id=689499 Maybe anyone would like to pick up the maintainance for this package? -- Sincerely yours Sascha Manns Community & Support Agent open-slx GmbH Web: http://community.open-slx.de -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] [reminder] openSUSE 12.1 RC 2 is next week

by openSUSE Roadmap Reminder

Hello all, openSUSE 12.1 RC 2 will be released next week, on Thursday 03 November 2011. Please submit your packages before Friday afternoon (UTC time) to make sure they will get included in this release. Leaf packages submitted during the week-end might also get accepted on Monday. For a quick overview of the openSUSE Roadmap, please see: http://en.opensuse.org/Roadmap Thanks, -- openSUSE Roadmap Reminder -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] Help with Mayavi

by Filipe Pires Alvarenga Fernandes

Hello, Recently vtk from the science repo was updated to version 5.8 and that broke my build of Mayavi: Building TVTK classes...: cannot connect to X server error: Bad exit status from /var/tmp/rpm-tmp.mkotMT (%build) Full log: https://build.opensuse.org/package/live_build_log?arch=i586&package=python-… If I understood it correctly I need to start an X-server, I tried the instruction I found here: http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks However, it did not work as expected. I guess that it might be a simple thing, but I'm still a beginner at "packaging". Can anyone help me understand what I should do ? Thank you for the attention, Filipe. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] Packaging Javascript libraries as part of web-applications

by Johannes Weberhofer

Hi! I have a general question regarding packaging of Javascript libraries as parts of application: Eg. phpmyadmin contains jquery in a specific version. Because phpmyadmin is GPL2+, jquery must also be licensed under the GPL (which is possible). licensing under the GPL implies, the source-code is made available with the package. Unfortunately, only the compressed code is packed with the phpmyadmin sources. The only "clean" way - in my opinion - is to package those libraries in seperate package, which makes packaging quite complex. I could think of packaging the libs under /use/share/js/libraryname/version.release in packages called libraryVersion.release and package those seperately. Of course, packaging is getting very complex... What do you suggest, regarding this problem? Best regards, Johannes -- Johannes Weberhofer Weberhofer GmbH, Austria, Vienna -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 6 months

[opensuse-packaging] skip subpackages

by Ilya Chernykh

Hi! I want to skip all subpackages in a very fat package. How can I do this quickly, and, desirably, with a condition depending on a set variable? I think about the file list: to prevent failure I would have to either add %exclude to all non-needed files (tens of them) or delete them after installation. Is there another way? There is no option in configure script to skip building the subpackages. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 7 months

[opensuse-packaging] Debian packaging?

by Uwe Drechsel

Hi, yes, I know, this list is named differently. Still I'm trying to build a .deb in BS from https://build.opensuse.org/package/show?package=vym&project=home%3Ainsilmar… Installing in Ubuntu 11.10 shows, that all files go to /share/vym and /share/doc/packages/vym while they should go to /usr/share/vym/ and /usr/share/doc/packages/vym Any hints what's missing? Is this a problem in my debian.rules or in BuildService? Thanks Uwe -- mathematician, n: Someone who believes imaginary things appear right before your i's. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 7 months

[opensuse-packaging] openSUSE:12.1 is split from factory

by Stephan Kulow

Hi, Before you find it during some surfing around on build.opensuse.org, I better tell you: we copied openSUSE:12.1 from factory now. This means we will build RC2 from there. This also means I will move my focus to that new project and leave factory for a while building as it is. Please submit your 12.1 fixes to openSUSE:Factory as usual, I will review them and forward to 12.1 as I see important bugs fixed. The rest can stay in Factory for 12.2. Reminder: checkin deadline for RC2 is october 28th. Afterwards is a long weekend for many in Bavaria. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org

10 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

openSUSE Packaging October 2011