[csw-maintainers] web visibility of packages

Ben Walton bwalton at opencsw.org
Mon Aug 15 02:07:04 CEST 2011


Excerpts from Maciej Bliziński's message of Sun Aug 07 05:38:27 -0400 2011:

Hi Maciej,

> {"maintainer_full_name": null, "version_string":
> "1.8.7p334,REV=2011.03.24", "basename":
> "ruby18-1.8.7p334,REV=2011.03.24-SunOS5.9-sparc-CSW.pkg.gz",
> "maintainer_email": "bwalton at opencsw.org", "mtime": "2011-04-01
> 17:42:37", "file_basename":
> "ruby18-1.8.7p334,REV=2011.03.24-SunOS5.9-sparc-CSW.pkg.gz", "arch":
> "sparc", "osrel": "SunOS5.9", "size": 1365872, "md5_sum":
> "688d3a5b038d172a36a4cba30272441f", "pkgname": "CSWruby18", "rev":
> "2011.03.24", "filename_arch": "sparc", "version":
> "1.8.7p334,REV=2011.03.24", "catalogname": "ruby18"}

I'd like to get more information than what is currently available.
I suspect that this will require a schema change and thus a full
re-index of the package tree.

The current database table presented at www/packages stores:

$software
$pkgname
$desc
$version
$vendorurl
$email
$maintlogin
$repourl

The things that I'm missing are $vendorurl and $repourl.  Is it
possible to extend pkgdb such that this is collected?  It would save
having to fetch each updated package, unroll it and extract the info
from it directly.  As the pkgdb rest calls will already be expensive,
I'd like to avoid this additional overhead if possible.

What do you think?

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302



More information about the maintainers mailing list