[Mageia-sysadm] perl modules shipped by mageia - the web site!

Jerome Quelin jquelin at gmail.com
Fri Mar 30 17:08:35 CEST 2012


so now that pkgcpan.mageia.org is up & running and serving the database
(thanks again!), i finally took some time to kickstart an idea i was
toying with: tracking the number of modules shipped by mageia over time.

i also created a very rough webpage for that, which i'd like to expand
in the future to a more consistent website.

cf attached tarball for the website.
(note: i'm not a web designer, any help & comments are welcome)

now, i'd like this website to be placed on mageia infrastructure.
benefits: stats will be updated on a regular basis, and this will allow
people to quickly see the trend, showing that mageia is perl-developer

to generate the site, it's a matter of running once a day:

    $ magpie webstatic -d /path/to/website

it doesn't take long (less than 5 seconds), and updates the statistics
besides generating the website.

note that /path/to/website will be wiped, so no other data than the
website needs to be put in this location. it also means that process
needs to have write access to the parent dir of /path/to/website

at this point in time, you are now eager to implement that. :) however,
there are 2 problems:

- "magpie webstatic" is implemented in latest release of magpie, which
  just hit cpan. the package is updated in svn & ready to be submitted,
  but it's release freeze. granted, magpie is a leaf package which is
  only used by mageia perl packagers.
  ==> do you think i can ask for a freeze push?

- mageia infrastructure is running mga1. so even if magpie is pushed
  according to previous point, the infra won't have it in their repos.
  and it also needs perl-ORDB-CPAN-Mageia & perl-RRDTool-OO which are
  also not available in mga1.
  ==> if magpie gets pushed, can it be installed on the infra? (by
      picking & installing the right rpms)


More information about the Mageia-sysadm mailing list