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
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
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
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
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
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
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
-----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
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
[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