October 2007 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Standard way to install a font?
by Paul Elliott 06 Nov '07

06 Nov '07

Is there a standard way (a macro perhaps), to install a font? I have a spec file written by someone else that puts the following in %post: [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1;\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1/adobestd35;\ [ -x /usr/bin/fc-cache ] && /usr/bin/fc-cache Is this correct? Works with all distros? -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

2 1

[opensuse-packaging] %debug_package issues with Suse only
by mrdocs＠scribus.info 01 Nov '07

01 Nov '07

Sent originally to -buildservice by mistake.... Hi, I have hit a weird issue when enabling %debug_package when wrapped inside something like this: %if 0%{?suse_version} %debug_package Build Requires: blah... %endif If %debug_package is enabled, the install portion fails on all Suse versions by seemingly unsetting RPM_BUILD_ROOT so the install part tries to install into /usr not /var/tmp/package/usr Package in question is: https://build.opensuse.org/package/show?project=home%3Amrdocs&package=gsview Now Mandriva seems to automagically enable debug packages, so there is no need to enable it in the spec file. This package has reliably built before on OBS on all rpm distros and arches. Is this a subtle difference in the rpm versions from FC. Mdk and Suse ? or could this be an OBS issue? Thoughts ? Thanks, Peter --------------------------------------------------------------------- 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] New rpmlint in BETA
by Dirk Mueller 29 Oct '07

29 Oct '07

Hi, [external people: ignore on] There will be a new rpmlint in BETA. It might produce new fancy fallout. Do not panic, I`ll be watching it. I`ll let you know if you have to fix something in your package by personal email. [external people: ignore off] Greetings, Dirk -- RPMLINT information under http://en.opensuse.org/Packaging/RpmLint --------------------------------------------------------------------- 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] insserving services
by Jan Engelhardt 28 Oct '07

28 Oct '07

Hi, some packages (e.g. cups), after installation, insert their service into the runlevel, others (e.g. apache2) do not. How is this accomplished in the %post sections of .spec files? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

5 8

[opensuse-packaging] Multiple KMP modules
by Andreas Schneider 28 Oct '07

28 Oct '07

Hi, I'm currently updating VirtualBox and building all the kernel modules now. https://build.opensuse.org/project/show?project=Virtualization%3AVirtualBox VirtualBox needs a kernel module (vboxdrv) loaded to work. But it has two additional kernel modules for installed guest (vboxadd, vboxvfs). Is it possible to add several KMP modules in one spec file or do I need an additional spec file? So hat I have virtualbox-kmp-default and virtualbox-kmp-guest-additions-default. -- andreas -- http://www.cynapses.org/ - cybernetic synapses

1 0

[opensuse-packaging] RPM packageing is too much like folklore.
by Paul Elliott 28 Oct '07

28 Oct '07

Folklore, like every village has its own version of the story, slightly different from every other village's version. There is plenty of documentation on writing a .spec file on the net, but is scattered across 1000 different web sites and mailing list archives. A lot of the documentation is obsolete in places. You can not go to one place and learn RPM packaging, instead you have to go prospecting like an anthropologist to find all the information that seems to be relevant to your problem. Every distro does it approximately the same, with enough differences to drive one mad! Will Linux Standard base or some big documentation writer ever come to save the day and bring order to this chaos? -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

3 2

[opensuse-packaging] how to convert pkg-config checks to BuildRequires (was: Re: openSUSE GNOME meeting (2007/10/25))
by Stanislav Brabec 26 Oct '07

26 Oct '07

Rodrigo Moya wrote: > - Stanislav had a tool to analyze pkg-config checks for automatically update > BuildRequires It's still unfinished and might be broken... I made my proof of concept public: http://pack.suse.cz/sbrabec/pkg-buildrequires/ Technical background and problems: - It's not easy to get package dependency data from configure.in. m4 expansion may occur and shell expansion may occur as well. Finally it's not easy to guess, which branch of code is actully active => The simplest way is modifying or wrapping of pkg-config itself. Solved. - RPM offers no way how to get data collected by %build back to the spec file preamble. We need a simple but enforcing way to perform this step manually. Still needs proper solution. Proposed usage: BuildRequires: pkg-buildrequires and replace %configure by %pkg_buildrequires_configure -- 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 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 1

[opensuse-packaging] rpm5.org
by Pascal Bleser 25 Oct '07

25 Oct '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I look at the "Team" presented on http://rpm5.org I notice several people involved in QA for several distributions, but no one for openSUSE/SLE*. Lack of time, lack of interest, technical reasons ? Thanks for enlightening me :) 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 iD8DBQFHH9iwr3NMWliFcXcRAtYqAJ4x9fkJ1Jb2nT0nTpyLAF3aLPemRQCgkH9I M3dXLk3Xuo0uVBNAUyT+074= =l3v5 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

10 17

[opensuse-packaging] Suggests/Enhances HOWTO?
by Nikolay Derkach 25 Oct '07

25 Oct '07

Hi, Is there any howto/guide on how to use these RPM tags? I couldn't find any, moreover I never saw a single package using them. Nevertheless, I recall there was an announcement on the list that these instructions were implemented [*]. So, could someone please clarify the situation? PS: are these patches included into the upstream RPM? [*] http://lists4.opensuse.org/opensuse-packaging/2005-12/msg00068.html -- Regards, Nikolay Derkach --------------------------------------------------------------------- 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] 2nd reminder to fix your packages for compiling with GCC 4.3
by Richard Guenther 23 Oct '07

23 Oct '07

[BCCed to devel, labs as not all people seem to be subscribed to opensuse-packagers] Hi, this is a reminder for you to have a look at your packages that fail in the BETA distribution (which has GCC 4.3 as its compiler). If you think that the compiler is at fault feel free to report these issues back to me or file a bugzilla for them. Builds with a slightly newer version of GCC for x86_64 and i586 are also available in the home:rguenther:playground build service project. Thanks, Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - 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

8 7

[opensuse-packaging] Re: [Research] Re: [devel] 2nd reminder to fix your packages for compiling with GCC 4.3
by Ruediger Oertel 22 Oct '07

22 Oct '07

On Mon, 22 Oct 2007, Miklos Szeredi wrote: > On Mon, 2007-10-22 at 15:08 +0200, Richard Guenther wrote: > > > this is a reminder for you to have a look at your packages that fail > > in the BETA distribution (which has GCC 4.3 as its compiler). If you > > think that the compiler is at fault feel free to report these issues > > back to me or file a bugzilla for them. > > A couple of my packages (and >100 others it seems) are failing with > > error: 'foo' was not declared in this scope > > I'm rather clueless about C++ issues, so I don't have a clear idea if > this is indeed a bug in all these programs or if it's a gcc problem. no these are really missing include files in your sources. What I've seen up to now were roughly 90% of either missing "#include <cstring>" or "#include <cstdlib>". > But even if these are bugs, wouldn't it have been prudent to make this a > warning, for couple of releases, before turning it into an error? well, "function not declared" has been an error in C++ before. What changed is that some files are not any longer pulled in automatically by others to get closer to the standard (please correct me here if I'm wrong). Unfortunately I don't see how a compiler should do something like "include this header but prefix all declared functions with a warning" ... -- with kind regards (mit freundlichem Grinsen), Ruediger Oertel (ro@novell.com,ro@suse.de,bugfinder@t-online.de) ---------------------------------------------------------------------- Linux Fatou 2.6.22.9-0.4-default #1 SMP 2007/10/05 21:32:04 UTC x86_64 Key fingerprint = 17DC 6553 86A7 384B 53C5 CA5C 3CE4 F2E7 23F2 B417 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

1 0

[opensuse-packaging] Re: [Research] Re: [devel] 2nd reminder to fix your packages for compiling with GCC 4.3
by Stephan Kulow 22 Oct '07

22 Oct '07

Am Montag 22 Oktober 2007 schrieb Miklos Szeredi: > On Mon, 2007-10-22 at 15:08 +0200, Richard Guenther wrote: > > this is a reminder for you to have a look at your packages that fail > > in the BETA distribution (which has GCC 4.3 as its compiler). If you > > think that the compiler is at fault feel free to report these issues > > back to me or file a bugzilla for them. > > A couple of my packages (and >100 others it seems) are failing with > > error: 'foo' was not declared in this scope > > I'm rather clueless about C++ issues, so I don't have a clear idea if > this is indeed a bug in all these programs or if it's a gcc problem. > > But even if these are bugs, wouldn't it have been prudent to make this a > warning, for couple of releases, before turning it into an error? As in "Warning: you obviously did not include all header files you need, but I invented some for you"? I don't think that would work. If 'foo' needs foo.h, you need to include it. If bar.h of gcc 4.1 happend to include it, there is no guarantee whatsoever that it will continue so. Greetings, Stephan --------------------------------------------------------------------- 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] Reminder to fix your packages for compiling with GCC 4.3
by Richard Guenther 18 Oct '07

18 Oct '07

On Wed, 17 Oct 2007, Holger Macht wrote: > On Wed 17. Oct - 17:53:53, Richard Guenther wrote: > > On Wed, 17 Oct 2007, Richard Guenther wrote: > > > > > On Wed, 17 Oct 2007, Holger Macht wrote: > > > > > > > On Wed 17. Oct - 13:09:30, Marcus Rueckert wrote: > > > > > On 2007-10-17 12:56:51 +0200, Holger Macht wrote: > > > > > > What would result in > > > > > > > > > > > > char *prop = (char*)"laptop_panel.num_levels"; > > > > > const char *prop = "laptop_panel.num_levels"; > > > > > > > > > > should fix it too no? > > > > > > > > Of course it does. > > > > > > > > I also have to change everything like: > > > > > > > > void testfunc(char *str); > > > > testfunc("foo"); > > > > to > > > > testfunc((char*)"foo"); > > > > > > No, the correct fix is to make testfunc take a const char *. > > > > So what about functions which modify their arguments and thus can't take a > const? For those it would be even more wrong to pass a constant string literal, the function would simply segfault in that case. For those you need to use char tmp[] = "foo"; bar (tmp); which constructs a stack temporary string with the contents "foo" and thus allows writing into it. Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - 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

1 0

[opensuse-packaging] libada41 build requirement problems under 10.3
by Günter Dannoritzer 17 Oct '07

17 Oct '07

Hi, I am building a package (ghdl) containing ADA code. Under openSUSE 10.2 I use the build requirements: - gcc-ada gcc41-ada libada41 For 10.1 and 10.0 I use the build requirements: - gcc-ada libada The build worked fine but neither of the two above works for 10.3. The error log says: error: Failed build dependencies: libada41 is needed by ghdl-0.26-3.1.x86_64 I looked into the distribution packages under: http://download.opensuse.org/distribution/10.3/repo/oss/suse/i586/ and there is a libada41 package. Can anyone give me a hint what I am doing wrong? Thanks for you help. Cheers, Guenter --------------------------------------------------------------------- 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] Reminder to fix your packages for compiling with GCC 4.3
by Richard Guenther 17 Oct '07

17 Oct '07

Hi, this is a reminder for you to have a look at your packages that fail in the BETA distribution (which has GCC 4.3 as its compiler). If you think that the compiler is at fault feel free to report these issues back to me or file a bugzilla for them. Builds with a slightly newer version of GCC for x86_64 and i586 are also available in the home:rguenther:playground build service project. Thanks, Richard. -- Richard Guenther <rguenther(a)suse.de> Novell / SUSE Labs SUSE LINUX Products GmbH - Nuernberg - 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

6 9

[opensuse-packaging] Duplicate -lang packages waste space
by Jan Engelhardt 15 Oct '07

15 Oct '07

Hi, I noticed that some -lang packages contain noarch data and hence should be produced as such, to reduce number of packages in the rpm metadata, as well as the space on DVD. For example: -rw-r--r-- 1 455 5200 597700 Sep 23 01:07 /lnk/103/i586/mc-lang-4.6.1-140.i586.rpm -rw-r--r-- 1 455 5200 597820 Sep 26 02:39 /lnk/103/ppc/mc-lang-4.6.1-141.ppc.rpm -rw-r--r-- 1 455 5200 597691 Sep 23 01:15 /lnk/103/x86_64/mc-lang-4.6.1-140.x86_64.rpm making the -lang package be built as noarch is an exercise left to the implementor. Running `lbuild-10.3 --target=noarch mc.spec` is a workaround, but of course it would be nicer if BuildArch: noarch in a subpackage in a specfile would only cause the subpackage to be noarch. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 9

[opensuse-packaging] libfoo-util , libfoo-bin or libfooN-[util|bin] ?
by Cristian Rodriguez 12 Oct '07

12 Oct '07

Hi folks: There are several libraries that ships binary utils that are not needed for the library to work by itself but the library packaging policy nor any other document covers the naming of this packages. so, how you think the should be called ? libfooN-util libfoo-util libfoo-bin libfooN-bin Comments :? -- "You don't have to burn books to destroy a culture. Just get people to stop reading them." --Ray Bradbury Cristian Rodríguez R. SUSE LINUX Products GmbH Research & Development --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

4 4

[opensuse-packaging] mDNSResponder requirement removal from packages
by Stanislav Brabec 11 Oct '07

11 Oct '07

Hallo. I just did a packaging change of avahi package and splitted binding devel packages. I reviewed all packages with explicit requirement of any avahi subpackage and did my best attempt to fix requirement to use correct subpackage. Many packages contain this ChangeLog entry: - Removed bogus dependency on mDNSResponder. These packages contain no single line referring to mDNSResponder, dns_sd or mdnsd. I guess, that for all these packages it was a relict of a SuSE 10.1 beta dependency breakage. If you will see breakage in older products, and your package does not use mDNSResponder directly, please don't fix it and let me know. It would be best to fix potential breakages globally by buildconfig. If your package uses one of Zeroconf libraries, but my guess was not correct, feel free to fix it. I fixed ~100 packages, so I did not try to rebuild them all before submit. -- 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 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

[opensuse-packaging] Broken xorg-x11-fonts and xorg-x11-fonts-core from 7.3?
by Rafał Miłecki 10 Oct '07

10 Oct '07

SSBqdXN0IHdhbnRlZCB0byB1cGdyYWRlIFhvcmcgaW4gbXkgb3BlblNVU0UgMTAuMyB1c2luZwpodHRwOi8vZG93bmxvYWQub3BlbnN1c2Uub3JnL3JlcG9zaXRvcmllcy94b3JnNzMvb3BlblNVU0VfMTAuMy8KCkV2ZXJ5dGhpbmcgZXhjZXB0aW5nIHR3byBwYWNrYWdlczoKeG9yZy14MTEtZm9udHMtNy4zLTEuNy5ub2FyY2gucnBtCnhvcmcteDExLWZvbnRzLWNvcmUtNy4zLTEuNy5ub2FyY2gucnBtCndhcyBmaW5lLgoKVGhlIGVycm9yIGlzOiAiaW50ZWdyaXR5IGNoZWNrIGhhcyBmYWlsZWQiIGZvciB0aGVzZXMgdHdvLgoKU2NyZWVuOiBodHRwOi8vaW1nNDA1LmltYWdlc2hhY2sudXMvaW1nNDA1LzI4MjgvaW50ZWdyaXR5Y2hlY2tmYWlsZWRwcDYucG5nCgotLQpSYWZhxYIgTWnFgmVja2kK---------------------------------------------------------------------To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.orgFor additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] please find flaws in my spec file, menu questions?
by Paul Elliott 09 Oct '07

09 Oct '07

Internal evidence suggests the following spec file originally came from kdevelop under mandriva. I am trying to fix it so that it work with the major rpm distros and also with opensuse buildservice. Please find fault with this spec file as I have modified it. I am concerned with the macros: %update_menus and %clean_menus in %post and %postun Are these macros Mandrakeisms? what package do these macros depend on? How should this be done for other distros? Also are the fonts installed correctly in %post and %postun? What other flaws can you find? -------------cut here with a chain saw---------------------------- # This spec file was generated by KDevelop # Please report any problem to KDevelop Team <kdevelop-devel(a)kdevelop.org> # Thanks to Matthias Saou for his explanations on http://freshrpms.net/docs/fight.html #Changed by Paul elliott so will work with opensuse buildservice #norootforbuild %if 0%{?suse_version} %if 0%{?suse_version} < 1030 %define _prefix /opt/kde3 %endif %endif %define name skylendar %define version 1.7.0 Name: %{name} Version: %{version} Release: 3%{?dist} Vendor: C. Gros License: GPL Summary: Astrology software for KDE Group: Sciences/Astronomy Packager: Paul Elliott BuildRoot: %{_tmppath}/%{name}-%{version}-build Source: skylendar-%{version}.tar.bz2 Patch: pe.diff Autoreqprov: on Requires: kdelibs3 Requires: postgresql Requires: perl Requires: perl-XML-DOM BuildRequires:autoconf automake libtool gcc-c++ BuildRequires: kdelibs3-devel %if 0%{?suse_version} %if 0%{?suse_version} == 1000 #intltool requires perl(XML::Parser) but opensuse 10.0 does not #know this BuildRequires: p_xmlpar %endif %endif %if 0%{?mandriva_version} BuildRequires: mandrakelinux-create-kde-mdk-menu %endif %if 0%{?suse_version} #suse here Requires: postgresql-pl Requires: qt3-postgresql %else %if 0%{?fedora_version} #fedora here Requires: postgresql-pl Requires: qt-postgreSQL %else %if 0%{?mandriva_version} #mandriva here Requires: postgresql-plpgsql Requires: libqt3-psql %else #unknown here. Requires: postgresql-plpgsql Requires: libqt3-psql %endif %endif %endif Autoreqprov: on %description Skylendar is an astrology program for KDE3, with SQL database management. %if 0%{?suse_version} %debug_package %endif %prep %setup %patch -p1 #remove next 2 lines when it is verified that it works wo them. #I do not have 64 bit system for testing. %if 0%{?suse_version} #suse here %{?suse_update_libdir:%{suse_update_libdir}} %{?suse_update_config:%{suse_update_config -f}} %endif %build export CFLAGS="$RPM_OPT_FLAGS" CXXFLAGS="$RPM_OPT_FLAGS" ./configure --prefix=%{_prefix} \ %if %{_lib} == lib64 --enable-libsuffix=64 \ %endif make %install make DESTDIR=$RPM_BUILD_ROOT install mkdir -p $RPM_BUILD_ROOT%{_menudir} %if 0%{?mandriva_version} kdedesktop2mdkmenu.pl %{name} Sciences/Astronomy $RPM_BUILD_ROOT/%{_datadir}/applications/kde/%{name}.desktop $RPM_BUILD_ROOT/%{_menudir}/%{name} kde %else cp src/%{name}.desktop $RPM_BUILD_ROOT/%{_datadir}/applications/kde/%{name}.desktop %endif mkdir -p $RPM_BUILD_ROOT%{perl_vendorlib} cp src/skif.pm $RPM_BUILD_ROOT%{perl_vendorlib} %clean %__rm -rf %{buildroot} %post /sbin/ldconfig;\ %{_bindir}/installskydb;\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1;\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -a %{datadir}/fonts/default/Type1/adobestd35;\ [ -x /usr/bin/fc-cache ] && /usr/bin/fc-cache %update_menus %postun /sbin/ldconfig;\ if [ "$1" = "0" ]; then\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -r %{datadir}/fonts/default/Type1;\ [ -x /usr/sbin/chkfontpath ] && /usr/sbin/chkfontpath -q -r %{datadir}/fonts/default/Type1/adobestd35;\ [ -x /usr/bin/fc-cache ] && /usr/bin/fc-cache\ fi %clean_menus %files %defattr(-, root, root) %doc AUTHORS COPYING ChangeLog README TODO %{_bindir}/* #%{_libdir}/menu/* %{_libdir}/menu/ %{_datadir}/apps/%{name} %{_datadir}/applications/kde/%{name}.desktop %{_datadir}/doc/* %{_datadir}/icons/* %{_datadir}/locale/* %{_datadir}/mimelnk/* %{perl_vendorlib}/skif.pm %changelog * Tue Oct 09 2007 Paul Elliott <pelliott(a)io.com> - 1.7.9-3 - norootforbuild indicates can be build wo root privs. * Fri Oct 05 2007 Paul Elliott <pelliott(a)io.com> - 1.7.0-2 - Change BuildRequires for SuSE - 64 bit conditional - --enable-libsuffix=64 if 64 bit - prefix for opensuse. - get rid of hardcoded /usr - makeinstall macro not good for fedora - %{_libdir}/menu/ is a empty directory. - patch pe.diff fixxes hardcode /usr/share/icons/hicolor/32x32/mimetypes/skif.png - which ignores prefix ------------cut here with a chain saw------------------------ -- Paul Elliott 1(512)837-1096 pelliott(a)io.com PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117

2 1

[opensuse-packaging] -lang subpackages
by Wolfgang Rosenauer 08 Oct '07

08 Oct '07

Hi, maybe I missed some announcement or document but I noticed that some packages (seems mainly Gnome ones) splitted the locale files out into an extra %{name}-lang package. What's the purpose of doing that? Is there any package conventions document about it? Is it to prepare an en-US only media and keeping the package sizes as small as possible? Wolfgang --------------------------------------------------------------------- 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] kernel-*.spec fixed strings are no fun
by Jan Engelhardt 07 Oct '07

07 Oct '07

Hi, the kernel-*.spec files contain a lot of hardcoded strings, such as 2.6.22.1 for what's currently cooking. This causes a major pain when trying to bump the version by oneself. All occurrences need to be replaced by more-or-less blunt scripts (simple perl -pe 's///'), since the .in files are not available. If these could please be added to the kernel-source pack, that would greatly simplify work. Moreover, I think that strings, where possible, should be replaced by rpm tags. For example this obvious one: Provides: kernel = 2.6.22.1-%source_rel (and other places) this can easily be replaced by %version-%source_rel. The other major thing being Name: kernel-default (and other places of course) which could be replaced - since the macro is already there - by Name: kernel-%build_flavor thanks, Jan -- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 5

[opensuse-packaging] kmp builds fail
by Jan Engelhardt 05 Oct '07

05 Oct '07

Trying to build some kmp removes module-init-tools from the buildsys, but which is BuildRequired:. I suppose lbulid does not properly expand macros, since BuildRequires: module-init-tools comes from /etc/rpm/macros.kernel-source that is inside the buildsys, and probably not installed yet. --------------------------------------------------------------------- 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] lbuild and the strangeness of kernels
by Jan Engelhardt 04 Oct '07

04 Oct '07

Hi, with lbuild-10.3, the following oddity happens: keeping kernel-bigsmp-2.6.22.9-ccj54 keeping kernel-default-2.6.22.9-ccj54 installing kernel-regular-2.6.22.9-ccj54 [...] keeping kernel-xen-2.6.22.9-ccj54 keeping kernel-xenpae-2.6.22.9-ccj54 [...] ----------------------------------------------------------------- ----- building kernel-syms.spec (user abuild) ----------------------------------------------------------------- ----------------------------------------------------------------- + exec rpmbuild -ba --eval '%define _srcdefattr (-,root,root)' /usr/src/packages/SOURCES/kernel-syms.spec error: Failed build dependencies: kernel-default is needed by kernel-syms-2.6.22.9-ccj54.i586 With lbuild-10.2, all is fine, even though sl10.3.conf is only slightly changed from sl10.2.conf to accomodate the different package names (I've did it myself before the novell sl10.3.conf was posted). Something related here? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 2

[opensuse-packaging] Library naming
by Jan Engelhardt 04 Oct '07

04 Oct '07

Hi, I notice, for example, -rw-r--r-- 1 455 5200 66727 Sep 22 00:02 libelf0-devel-0.8.9-17.i586.rpm while I agree with the new naming scheme (libelf0), I do not for -devel packages that cannot reasonably be installed alongside each other. Think of libelf0-devel and libelf1-devel which both provided a file with the same path. Without starting religious issues, would not it be better to just continue on naming such devel packages libelf-devel, without a number, like Debian? That would also reduce newly Obsoletes: tags, because now, a libelf1-devel would need an Obsoletes/Conflicts: libelf0-devel, and that's not really helping. In cases where -devel packages can be coinstalled (imagine libxml2 and a fictious libxml3 with /usr/include/libxml2 and /usr/include/libxml3, respectively), the number should be kept of course. Just a suggestion, it's too late for 10.3 anyway. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

6 8

[opensuse-packaging] lbuild definition for 10.3
by Jan Engelhardt 02 Oct '07

02 Oct '07

Hi, has someone from Novell already created a /usr/lib/lbuild/configs/sl10.3.conf/factory.conf configuration and would like to share it? thanks, j --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 8