Next | Query returned 26 messages, browsing 21 to 30 | previous

History of commit frequency

CVS Commit History:


   2012-10-28 07:31:10 by Aleksej Saushev | Files touched by this commit (600)
Log message:
Drop superfluous PKG_DESTDIR_SUPPORT, "user-destdir" is default these days.
   2012-10-03 23:59:10 by Thomas Klausner | Files touched by this commit (2798)
Log message:
Bump all packages that use perl, or depend on a p5-* package, or
are called p5-*.

I hope that's all of them.
   2011-08-14 18:06:13 by OBATA Akio | Files touched by this commit (268)
Log message:
Revision bump after updating perl5 to 5.14.1.
   2010-08-21 18:37:14 by Stoned Elipot | Files touched by this commit (1724) | Package updated
Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.10.1 -> 5.12.1.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=..."), minus the packages updated after
the perl package update.

sno@ was right after all, obache@ kindly asked and he@ led the
way. Thanks!
   2008-10-19 21:19:25 by Havard Eidnes | Files touched by this commit (1179)
Log message:
Bump the PKGREVISION for all packages which depend directly on perl,
to trigger/signal a rebuild for the transition 5.8.8 -> 5.10.0.

The list of packages is computed by finding all packages which end
up having either of PERL5_USE_PACKLIST, BUILDLINK_API_DEPENDS.perl,
or PERL5_PACKLIST defined in their make setup (tested via
"make show-vars VARNAMES=...").
   2008-06-23 05:35:35 by David Brownlee | Files touched by this commit (3) | Imported package
Log message:
import p5-HTTP-Async-0.09

Although using the conventional LWP::UserAgent is fast and easy it
does have some drawbacks - the code execution blocks until the
request has been completed and it is only possible to process one
request at a time. HTTP::Async attempts to address these limitations.

It gives you a 'Async' object that you can add requests to, and
then get the requests off as they finish. The actual sending and
receiving of the requests is abstracted. As soon as you add a
request it is transmitted, if there are too many requests in progress
at the moment they are queued. There is no concept of starting or
stopping - it runs continuously.

Whilst it is waiting to receive data it returns control to the code
that called it meaning that you can carry out processing whilst
fetching data from the network. All without forking or threading
- it is actually done using select lists.


Next | Query returned 26 messages, browsing 21 to 30 | previous