2013/4/3 Peter FELECAN <[email protected]>: > Quite useful. However, link the package to the description otherwise you > have a cycle... e.g. > > http://buildfarm.opencsw.org/pkgdb/catalognames/a2ps/ to > http://buildfarm.opencsw.org/pkgdb/srv4/0081cafba415a45801d8191ebdbfee56/ to > http://buildfarm.opencsw.org/pkgdb/catalognames/a2ps/
This loop is intentional, the link back to a2ps is a link to the catalogname, because the thing under link is a catalogname. > Also, back-links would be useful. You mean, some sort of a common navbar? It's probably doable with includes, but the templates we're using are Cheetah templates[1] and their "#include" seems messed up to me. I asked about it on their mailing list: http://permalink.gmane.org/gmane.comp.python.cheetah/2825 ...and got zero answers. I think that if we want to improve our templates, we should switch a different engine with sane #include, for example jinja2. In the meantime, everybody's welcome to tweak the existing templates. For information how to set up pkgdb and releases, see the README file[2] (I just updated it). By the way, if anyone comes up with a way to set these scripts up using lighttpd, please contribute your setup instructions! It would be a better fit on small setups like virtual machines at home. Maciej [1] https://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/lib/web/templates [2] https://sourceforge.net/apps/trac/gar/browser/csw/mgar/gar/v2/lib/web/README _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
