On Tuesday 12 May 2009 09:45, Adam Gołębiowski wrote: > Elan Ruusamäe pisze: > > On Friday 08 May 2009 13:27:23 Elan Ruusamäe wrote: > >> On Friday 08 May 2009 13:19:04 Tomasz Pala wrote: > >>> On Fri, May 08, 2009 at 12:33:46 +0300, Elan Ruusamäe wrote: > >>>>>> please give (at least) one sample, so i could write 404 handler in > >>>>>> apache to solve this problem. > >>>> > >>>> i mean, a url to resource which contains link to _that_ link. > >>> > >>> Like this? > >>> > >>> http://lists.quagga.net/pipermail/quagga-dev/2009-April/006507.html > >> > >> yep. > >> > >> for now added redirect rules: > >> > >> RedirectMatch permanent ^/cgi-bin/cvsweb/SOURCES/(.*)$ > >> http://cvs.pld-linux.org/cgi-bin/cvsweb/SOURCES.old/$1 RedirectMatch > >> permanent ^/cgi-bin/cvsweb\.cgi/SOURCES/(.*)$ > >> http://cvs.pld-linux.org/cgi-bin/cvsweb.cgi/SOURCES.old/$1 > >> > >> is this sufficent, or we should rather redirect to new location in > >> /packages? > >> > >> i mean if you gave old link, then you likely want to point it to the > >> resource available at that time, which this SOURCES.old redirection > >> satisfies. however this will all go void if the SOURCES.old tree is > >> removed someday. > > > > ping? > > Seems fine for me, I provided URLs like: > > http://cvs.pld-linux.org/SOURCES/foo.patch > http://cvs.pld-linux.org/SOURCES/foo.patch?rev=HEAD > > as in: > http://pecl.php.net/bugs/bug.php?id=9697 > > and the redirect works for these as well.
the question was rather, should redirect go to /SOURCES.old, or find the location where it was moved in /packages/%{name}, as if we discard /SOURCES.old oneday, the links go broken. as i don't know will /SOURCES.old stay or not? -- glen _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en