Re: man-db without cache update (no cron or systemd *.timer)

2014-10-15 Thread Peter Schiffer 

On 10/15/2014 04:47 PM, Chris Adams wrote:

Once upon a time, Jan Chaloupka jchal...@redhat.com said:

there has been a discussion about if we need cache for man-db for users
which use man pages or update system only from time to time and thus
don't need to update cache every day. man-db as it is now depends on
systemd which brings another set of packages. The use case is I just
want to read man page. So I install man which on the other hand download
another set of packages. I want to read man page and it downloads systemd..


On the majority of systems these days, is it really an issue to cache
man pages anymore?  I mean, back when a long man page (thinking about
some of the perl documentation for example) could take a while to
render, it mattered.  Now however, systems are much much faster, and we
expect GUI web browsers to render vastly more complicated content in a
fraction of a second.

Maybe the time has come to just stop caching man pages at all, or at
least make that functionality optional (and non-default)?



Hello,

I would add some noteworthy information:

 * the man-db cron/timer script is taking care of man DB containing
only the man page title and short description i.e., the first NAME
section of the man page. This DB is speeding up the searching in
mentioned section with the man -k command. It is not used for
displaying man pages or doing the full text search with man -K command
and it is not required for normal usage of man command (man -k should
also work without this DB).

 * Debian is updating this DB via deb hooks (or how it is called)
during package installation/update and via daily cron script for man
pages installed outside of package manager.

 * updating this DB is usually pretty quick, but creation can take some
time..

 * man pages cache, pre-formatted man pages stored on disk in plain
text, called cat pages in man-db context, is not used in Fedora.

peter

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

I am going to un-orphan stgit package

2012-10-19 Thread Peter Schiffer 

Hello all,

I've taken the stgit package ownership in F16 and EL5/6 branches, and I 
am going to open the review ticket for this package.


Package was orphaned because lack of maintainer:
http://lists.fedoraproject.org/pipermail/devel/2011-November/158900.html

peter
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

Re: How to update GMP-using packages

2011-10-18 Thread Peter Schiffer 
Hello,

it will be better, if you could wait until the f17-gmp tag will be 
merged into rawhide.

In general, it's not a problem, when you make build _between_ our two 
builds, but it's problem, when you make build after our second build and 
before merging f17-gmp into rawhide. In that case, we have to rebuild 
your package again.

Currently, one issue is holding us, but it should be solved soon. We 
should start second waive of rebuilds this week.

peter

On 10/17/2011 11:52 PM, Jerry James wrote:
 How should those of us with gmp-using packages manage updates while
 the update to GMP 5.x is underway?  I've got a handful of updates I
 want to build for Rawhide at some point, but I don't want to cause
 problems.  Should I wait until the GMP update is done and the packages
 are all tagged, or go ahead now?  If the former, is there an ETA?
 Thanks,
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel

gmp rebase in rawhide

2011-10-10 Thread Peter Schiffer 
Hello,

there is currently ongoing rebase of gmp package in f17-gmp dist tag 
targeting rawhide.
Because of this, we have to rebuild all dependencies twice (at first 
with compatibility package, then without it).

All packages depending on gmp can be found here:
https://fedorahosted.org/rel-eng/attachment/ticket/4929/dependencies.txt

This is only information email, no action from your side is required.

peter
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel