June 2008 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] On debuginfo and optflags
by Christian Morales Vega 14 Jun '08

14 Jun '08

I just noted that while /usr/lib/rpm/x86_64-linux/macros says optflags are "-O2 -g -fmessage-length=0 -D_FORTIFY_SOURCE=2", the buildconfig on OBS says they are "-fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -O2". Why are they different? Should not "macros" files be updated? And why "-g" was removed from the OBS optflags? Doesn't this makes debuginfo packages unusefull? Also, are debug packages not shown on http://download.opensuse.org/repositories/ anymore? My old packages still show them , but new ones don't... even if I can download them from http://build.opensuse.org/ So, what is the official politic about debuginfo packages? Should we add "-g" manually when we want them? When someone would not want a debuginfo package? Or should we just never use %debug_package? --------------------------------------------------------------------- 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] Branding packages for openSUSE 11.0
by Stanislav Brabec 13 Jun '08

13 Jun '08

Hallo. Branding comments from the openSUSE 11.0 release packages were collected and put into wiki page: http://en.opensuse.org/Branding_of_openSUSE_11.0 Feel free to fix these notes for your packages, but don't forget to do the same in your packages: http://en.opensuse.org/SUSE_Package_Conventions/Branding#Spec_file_comments I have also created a simple branding guide, which should help to people searching for "Branding": http://en.opensuse.org/Branding -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 966, +49 911 740538747 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- 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] Installing plugins in case of pre-conditionsfulfilled
by Michal Marek 13 Jun '08

13 Jun '08

Dominique Leuenberger napsal(a): >>>> On 13.06.2008 at 12:24, Michal Marek <mmarek(a)suse.cz >> Recent libzypp undestands >> >> Supplements: packageand(libproxy:kde-something) > > What do 'not-so-recent' libzypp to with those Supplements? And other > packagers? I'd assume they just ignore them, right? I think it will just check for a package named 'packageand(libproxy:kde-something)' and do nothing after not finding it. Other package managers will either behave the same or not look at the supplements tag at all. Michal --------------------------------------------------------------------- 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] Installing plugins in case of pre-conditionsfulfilled
by Dominique Leuenberger 13 Jun '08

13 Jun '08

>>> On 13.06.2008 at 12:24, Michal Marek <mmarek(a)suse.cz> wrote: >> if libproxy is selected and kde, install the kde plugin >> if libproxy is selected and gnome, install the gnome plugin > > Recent libzypp undestands > > Supplements: packageand(libproxy:kde-something) Thank you very much! That was exactly what I was looking for ;) Will try to add those statements this evening to the spec file. What do 'not-so-recent' libzypp to with those Supplements? And other packagers? I'd assume they just ignore them, right? Dominique --------------------------------------------------------------------- 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] Installing plugins in case of pre-conditions fulfilled
by Dominique Leuenberger 13 Jun '08

13 Jun '08

Hello, I'm packaging up libproxy in my home. It is a library with many plugins, like gnome, kde, networkmanager. I would like to have the plugins automatically selected on installation of libproxy, if some other requirements are set. like: if libproxy is selected and kde, install the kde plugin if libproxy is selected and gnome, install the gnome plugin Is something like this possible? I assume it will only be supported by zypper/YaST, but that's ok for me... people using RPM should know by their own anyhow what they do. The plugins of course have the correct Requires: set against their libs (gnome, kde, NM)... but that's the other way round. Thanks for your help.. I hope I could express what I try to achieve. Dominique --------------------------------------------------------------------- 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] [Announcement] Ports for SuSEfirewall added via packages
by Lukas Ocilka 11 Jun '08

11 Jun '08

Hi, I'd like to announce one major change in openSUSE 11.1 / SLE 11: In the past, YaST Firewall had a special SuSEFirewallServices library that covered the main services for YaST Firewall UI. See a small example of Samba Server: "samba-server" : $[ "name" : _("Samba Server"), "tcp_ports" : [ "netbios-ssn", "microsoft-ds" ], "udp_ports" : [ "netbios-ns", "netbios-dgm" ], "broadcast_ports" : [ "netbios-ns", "netbios-dgm" ], ], This statically-defined library has been obsoleted by feature "Service Definitions Added via Packages" since openSUSE 10.3, openSUSE 11.0 still contains these definitions but some have been already replaced with the new dynamically-defined services. All statically-defined services were dropped in openSUSE 11.1 / SLE 11, SuSEFirewallServices will only provide conversion to the new type of services if possible. Please, make sure your packages provide service definitions for SuSEfirewall2. See also: http://en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Packages There are still some bugs (enhancements) open (untouched) requesting to add these services: #251663, #247344, #247359, #247355, #251657, #247368, #247363. Feel free to add more :) Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

2 3

[opensuse-packaging] New check in RPM build
by Lukas Ocilka 09 Jun '08

09 Jun '08

Hi, I've learned today that an RPM package can Provide and Require the same symbol but then the package is in conflict with itself and cannot be installed [unless --nodeps is used?] (thx to mmarek and his lecture on RPM today). If we can't fix the behavior, would it be possible to add one more check to the RPM build, please :)? This check should go through all RPM:Provides and RPM:Requires and report an error when the same string is found in both. Thx && Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

7 9

[opensuse-packaging] Shared Library Packaging Policy for alternate implementations?
by Ludwig Nussel 06 Jun '08

06 Jun '08

Hi, The Shared Library Packaging Policy says that the name of a library package is to be derived from the library's SONAME. What if there is a compatible alternative implementation of the library? Of course it has the same SONAME. Reusing the same package name would result in version confusion though. Are there any recommendations for naming packages of such alternative implementations? cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 11

[opensuse-packaging] KDE4
by Dirk Stöcker 06 Jun '08

06 Jun '08

Hello, for openSUSE 10.2 KDE 4 and KDE 3 could be installed in parallel. Now the KDE:KDE4 repository seems to be the base for Factory and the the spec files include "Replaces" tags, which disable parallel installation: E.g. kde4-ksudoku replaces "ksudoku" package (same for other packages). Could this please be changed, so that these replaces only work for >= 11.0? Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- 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] Variables in %Files Section
by Andre Hübner 04 Jun '08

04 Jun '08

Hi List, simple Question. On top of spec i declare Variable: %define HOSTNAME_SHORT `/bin/hostname -s` As %{HOSTNAME_SHORT} I can use it in %install or %post section with success but i get an error in %files section. I get error: Processing files: mailgraph-1.14-1 error: Two files on one line: /my/path/`/bin/hostname error: File must begin with "/": -s`/subpath/file.txt What could be the problem? Thank you Andre --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 8