Tcl packaging guidelines proposal
by Michael Thomas
I sent this proposal to f-m-l about a week ago to gather comments, and
there were no serious disagreements with the proposal which have not yet
been addressed (thanks to Tibbs and Toshio for their feedback).
Basically, I want to establish a set of guidelines for packaging Tcl
extensions, as we already have guidelines for other popular scripting
languages. In addition to making Tcl packages more consistent with each
other, it will also help work toward fixing my pet-peeve bug (bz #226893)
http://fedoraproject.org/wiki/PackagingDrafts/Tcl
Please let me know if I need to do anything to help get these draft
guidelines adopted.
Thanks,
--Wart
15 years, 5 months
Packaging/ScriptletSnippets, fonts section: no "|| :" at the end of the fc-cache call?
by Thorsten Leemhuis
Hi all,
the Fonts section on
http://fedoraproject.org/wiki/Packaging/ScriptletSnippets
contains this:
> Use this when your package installs new fonts.
>
> {{{
> %post
> if [ -x %{_bindir}/fc-cache ]; then
> %{_bindir}/fc-cache %{_datadir}/fonts
> fi
> %postun
> if [ "$1" = "0" ]; then
> if [ -x %{_bindir}/fc-cache ]; then
> %{_bindir}/fc-cache %{_datadir}/fonts
> fi
> fi
> }}}
Is there a specific reason why there is no "|| :" at the end of
"%{_bindir}/fc-cache %{_datadir}/fonts"? I think there should be one, as
this happened to me during a F-7 -> rawhide update (that's still in
progress while I'm writing this mail, so more errors might show up):
> Updating : bitstream-vera-fonts ################### [ 383/1850]
> /usr/share/fonts/default/Type1: failed to write cache
> /usr/share/fonts/default/ghostscript: failed to write cache
> error: %post(bitstream-vera-fonts-1.10-8.noarch) scriptlet failed, exit status 2
[...]
> Updating : fontconfig ################### [ 416/1850]
> /usr/share/fonts/default/Type1: failed to write cache
> /usr/share/fonts/default/ghostscript: failed to write cache
> /usr/share/X11/fonts/Type1: failed to write cache
> error: %post(fontconfig-2.4.2-5.fc8.x86_64) scriptlet failed, exit status 3
[...]
> Updating : dejavu-lgc-fonts ################### [ 548/1850]
> /usr/share/fonts/default/ghostscript: failed to write cache
> error: %post(dejavu-lgc-fonts-2.19-1.noarch) scriptlet failed, exit status 1
> Updating : liberation-fonts ################### [ 549/1850]
> /usr/share/fonts/default/ghostscript: failed to write cache
> error: %post(liberation-fonts-0.2-1.fc8.noarch) scriptlet failed, exit status 1
CU
knurd
15 years, 8 months
kernel mod package howto?
by Neal Becker
I'm submitting blcr which builds a kernel mod. Where can I find info on
packaging for kernel mods? Examples?
15 years, 9 months
tex related packages names
by Patrice Dumas
Hello,
I propose tex packages to be named
tex-something
instead of
tetex-something
I also think that it is not worth renaming existing packages with
tetex-, at least for now, maybe later, but instead have them
Provides: tex-something = %{version}-%{release}
--
Pat
15 years, 9 months
Python Egg Guidelines
by Toshio Kuratomi
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
I've finished a first draft of guidelines for using python eggs.
There's one open question -- whether we should be creating eggs for
upstreams that do not create them by default. I think the answer to
that is no except for one special case but others might disagree.
The rest of it is pretty straightforward; made longer by the addition of
copious examples. Take a look and give feedback. The Packaging
Committee will vote on this on Tuesday (next week's packaging meeting.)
https://fedoraproject.org/wiki/PackagingDrafts/PythonEggs
PS: We already have a couple of cases where we need to apply these
guidelines
* Review for parallel installable python-sqlalchemy0.3:
https://bugzilla.redhat.com/show_bug.cgi?id=257381
* Request for python-cherrypy-3.0 upgrade which needs a
python-cherrypy2 compat package for TurboGears.
https://bugzilla.redhat.com/show_bug.cgi?id=224683
* Request to add egginfo to docutils (which is a departure from upstream).
https://bugzilla.redhat.com/show_bug.cgi?id=256541
- -Toshio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFG1MfaX6yAic2E7kgRAmIlAJkBMOooviBZHGZhkg+Anh5kBQvDkACeIXLq
poCNwcUzHDbE8DN8EHU+58g=
=NZPE
-----END PGP SIGNATURE-----
15 years, 9 months
overview of all Package Guidelines or use CategoryPackageGuidelines
by Till Maas
Hi,
is there a page in the wiki that simply lists all existing guidelines for
packages in Fedora? I guess not. Therefore I suggest to add all these
guidelines to CategoryPackageGuidelines. I cannot do this myself, because I
cannot change the regarding wiki pages.
Regards,
Till
15 years, 9 months
