public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-dev@lists.gentoo.org
Cc: ycarus@zugaina.org
Subject: Re: [gentoo-dev] Stats test server running, please check it out
Date: Wed, 12 Aug 2009 14:31:48 +0200	[thread overview]
Message-ID: <4A82B634.2020303@hartwork.org> (raw)
In-Reply-To: <4A80CCE9.6020708@gentoo.org>

Federico Ferri wrote:
> 2nd: how to improve the output: you could make every data an
> hyperlink: that would help understand better the contents
> example:
> Archs:
>   hyperlink arch name to wikipedia perhaps

Done, linking to

  http://packages.gentoo.org/arch/${arch}


> CFLAGS
>   can link the flag name to GCC user guide relevant section, or to
> http://en.gentoo-wiki.com/wiki/CFLAGS#<flagname>
> same for other flags and MAKEOPTS

Later, server seems down.


> FEATURES
>   can link feature to make.conf man page:
> http://linuxreviews.org/man/make.conf/ (unfortunately this man page is
> rendered with no anchors over variable/features, so you could do
> better ^__^

Done,  linking to
http://smolt.hartwork.org:45678/static/man/man5/make.conf.5.html#${feature}

If anyone feels like playing with  manpage-screen.css  please do and
come back to me.

Also, the man page does not seem to list these features:

  cvs
  preserve-libs
  split-debug
  splitdebug
  unmerge-logs

Either people use invalid features (you tell me) or the man page needs
an update.  Maybe both ("split-debug" vs "splitdebug")?


> USE flags
>   can link to
> http://gentoo-portage.com/Search?search=&use=<useflagname> (now
> appears down)

Still down, linking to

  http://gpo.zugaina.org/Search?search=&use=${use}

for now.


> System profiles:
>   can link to profiles in cvs

Are you sure about this?  Will that be fun to look at?


> Package atoms can link to packages.g.o or to gentoo-portage.com

Done, linking to

  http://packages.gentoo.org/package/${CATEGORY}/${PN}


To be able to link all packages properly we'd need a version of
http://gpo.zugaina.org/  that includes the trees "gentoo" and "funtoo".

ycarus, could the server handle that load-wise?  would it be easy to
extend the current service or set up an all-packages-version in parallel?



Sebastian



  parent reply	other threads:[~2009-08-12 12:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-10 10:08 [gentoo-dev] Stats test server running, please check it out Sebastian Pipping
2009-08-10 10:57 ` Sebastian Pipping
2009-08-10 20:46 ` Sebastian Pipping
2009-08-10 21:11 ` [gentoo-dev] " Mark Bateman
2009-08-10 21:18   ` Sebastian Pipping
2009-08-10 21:16 ` [gentoo-dev] " Dirkjan Ochtman
2009-08-10 22:46   ` Sebastian Pipping
2009-08-11  1:44 ` Federico Ferri
2009-08-11 16:44   ` Sebastian Pipping
2009-08-11 17:21     ` Federico Ferri
2009-08-12  4:25   ` Sebastian Pipping
2009-08-12 12:31   ` Sebastian Pipping [this message]
2009-08-12 15:19     ` [gentoo-dev] " Duncan
     [not found]     ` <4A83026E.6000906@zugaina.org>
2009-08-12 18:54       ` [gentoo-dev] " Sebastian Pipping
2009-08-12 20:55     ` Robert Buchholz
2009-08-12 22:22       ` Sebastian Pipping
2009-08-13 14:30         ` Sebastian Pipping
2009-08-15  1:49         ` Sebastian Pipping
2009-08-11 19:57 ` [gentoo-dev] " Christian Faulhammer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A82B634.2020303@hartwork.org \
    --to=webmaster@hartwork.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ycarus@zugaina.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox