On Sat, 2013-05-25 at 21:08 +0200, Michael Stapelberg wrote: > I thought about this a little bit and the preferred way to implement > this is to have a redirect which would then just prepend (or append, > doesn’t matter) package:foo to the search term. That way, there is only > one interface to DCS to document/take care of. I hadn't though about a redirect, thanks for the idea. > Furthermore, it would be good to make this redirect automatic using a > tiny bit of JavaScript, i.e. having something like: ... > …and having a bit of JavaScript code which would delete the package > field before submitting and adding package:foo to the q input field. > > This saves a redirect which is moderately costly on good internet > connections but hugely painful on mobile connections. Also, it decreases > load on the server which performs the actual redirect. That is a good idea, though the redirect will still be needed for non-JS clients and for folks who turn off JS in their browser. > As for which server to use, I’d vote for the PTS code handling the > redirect, since the PTS is the one who needs the feature :). If for some > reason this is super-complicated within the PTS, I am not dead set on > this, but I would like to hear a decent reason if I should implement > that code within DCS. I'll implement that on the PTS side, there are already some CGIs there. > See http://codesearch.debian.net/faq — all sid source packages are > indexed. Due to quite a bit of CPU time required for this, the index is > only updated once a week, typically on friday. This currently is a > manual process, but I intend to automate it real soon. Ok, so I will only put the search box on packages that are in sid. Please let us know if this expands to other suites. What do you think of the idea in general? Will you be able to handle the (possibly) increased search traffic? Any other thoughts? -- bye, pabs http://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part