Re: experimental tex-common packages with triggers support
Hi,
On Wed, Jul 02, 2008 at 05:19:47PM +0200, Hilmar Preusse wrote:
> On 01.07.08 Michael Banck (mbanck@debian.org) wrote:
> > Norbert Preining wrote:
> > > I have uploaded tex-common 1.12 to experimental. This release
> > > contains triggers support. But as long as packages shipping
> > > updmap.d and language.d files are rebuild we wont profit.
> >
> > That's great, but I'm wondering whether this also includes trigger
> > support for mktexlsr?
> >
> IIRC Norbert decided not to implement triggers for mktexlsr for now,
> as the command does not need that much system resources.
Hrm, my mail was mainly motivated by the gprolog build on the Debian
GNU/Hurd buildd. It installed half/all of texlive, failed very early in
configure, and removed all of it. It took more then 24 *hours* to do
that, and as I saw those "mktexlsr" messages for most of that time, I
assumed that was the culprit, maybe. It could be that mktexslr does
something which turns out to be pathological on hurd-i386 only.
> > Also, will this be in lenny?
> >
> It is in experimental now. How much time needs a package to be in
> experimental until one can consider it is good enough for unstable?
> How many users do we have for the new version? Can we assume from the
> not appearing bug reports, that the package is stable?
Well, the usual rules for experimental apply - few people use it unless
really pushed for it. If you did not get any feedback, assuming that
everything is fine is not warranted. On the other hand, as I guess you
can easily back out the feature again in case of trouble, uploading it
to unstable now that you did not get any negative feedback (and possibly
revert it in case you then get some) looks alright to me.
Michael
Reply to: