Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • My biased view of this is that the up-to-date perl is mainly due to two factors:

    - perl going extreme lengths to be backward compatible (cf. rjw1's link).
    - The debian-perl team and the debian perl-package-maintainer(s) being simply awesome.

    I think the second point is actually somewhat more important. From my point of view as an interested bystander, the debian-perl maintainers seems to be a group of motivated, diligent, clueful, friendly and welcoming people who stem a great load of work collaboratively. The

  • from http://en.wikipedia.org/wiki/Debian [wikipedia.org]

    Software packages in development are either uploaded to the project distribution named unstable (also known as sid), or to the experimental repository. Software packages uploaded to unstable are normally versions stable enough to be released by the original upstream developer, but with the added Debian-specific packaging and other modifications introduced by Debian developers. These additions may be new and untested. Software not ready yet for the unstable distributio

    • Thanks, but that doesn't answer the "why" for this case. I roughly understand the procedure, but I had no idea what the details for Python are, and why it's still in experimental, not even in unstable. I think that Bob's link did reveal the causes, for 2.6. 3.1 remains a mystery.

      • I guess for experimental repository, you will have to ask the package maintainer(s) directly.
  • It's really the only sensible answer. Someone please inform the Python community that they can steal our angst now.