Re: Bug#612120: www.debian.org/ports/kfreebsd-i386 is missing
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Le 05/02/2011 22:39, Samuel Thibault a écrit :
> Simon Paillard, le Sun 06 Feb 2011 03:30:48 +0100, a écrit :
>> On Sun, Feb 06, 2011 at 03:25:10AM +0100, Samuel Thibault wrote:
>>> Wolodja Wentland, le Sun 06 Feb 2011 01:46:09 +0000, a écrit :
>>>> http://www.debian.org/ports/kfreebsd-i386/ is missing and results in a
>>>> 404.
>>>
>>> Yes, that's expected, it's http://www.debian.org/ports/kfreebsd-gnu/ for
>>> both.
>>> Where did you see that bogus URL?
>>
>> http://debian.org/releases/squeeze/
>> We link according to the arch name.
>
> Ok, that's actually collusion. In the debian manual, we separate arch
> name from port website name.
Hi kFreeBSD team,
We are wondering if the kfreebsd-i386 and kfreebsd-amd64 would deserve
their own http://www.debian.org/ports/ pages. It may be the more
consistent approach regarding existing directory name (alpha, amd64,
arm, hppa, i386, ia64, m68k, mips, powerpc, s390, sparc, sparc64, etc.)
but this choice is up to you.
If there is no point in maintaining both the ports/kfreebsd-amd64 and
ports/kfreebsd-i386 pages, we could try to tweak the auto-generated
links about kfreebsd-amd64 and kfreebsd-i386 to actually point to
ports/kfreebsd-gnu, but since those links maybe automatically generated
in other documents like release-notes or installation-guide, we may also
need to prepare a 301 redirection from ports/kfreebsd-amd64 and
kfreebsd-i386.
Please let us know what is your preferred approach.
Regards
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJNT2wAAAoJELgqIXr9/gnyrUEP/ReFM0BIeQSQ+O/xDsN0kZN4
MWvSa5aLPuB3mfxFpUMzuZe+HtOSSBj5yMB1m7g2QgYGJm2mDJVCsd4vF3wA9F8n
50pGBy1KjGjw/4I6H1r0h71NBn4O9HPMWXGBDVNPuTb3Jxq329YjTeiB4KMW0LGy
oKG1xfVNl0RS9iY4+zygCRucweMZRxaHUXy7KJGsUTdzqh9dQlT+mu4Bmf1kE/rE
oT8NMJo3p6twaPTSRxysY56v7wCLAc3QCJEHXXiYKuVPibVVe6GYWWsYIHaqc+wI
oFwAPNl8wSjvrRW8jrqVuWKnKVWRCR88wlKLVvD03chheaPzQSGINTB9wDklaAaj
SZXJQlf3JDo5e0rRg4DzZoPjoe0C7FANx+lK9/2oF/R4Mi+o1hS3Cf7K7ao7O3M5
kCYMd/vgpWtnD+1+HXX9+cwHuggpov9+2YPYaFJU4XitsTVWSAntvaEBxiSvHEPp
VcooOjQo9REYy/GFfzq7ZP8n0YrQb+T0Pz0EiMWXGal3xAn9JXvOJLcK4x5mG69b
CZvEUoJFaXjNj6E6JZSCdIcOqZNFw7MD7k7CrPx1qu++XwIadAHe1vH217iEbtUz
SiQD/3Glw1qS9Idx6nhgI/oYX7SW/pNX/sWrVMsv+MpXcgmZTOvHEq9GPoqHo1id
ydetxPK3xuVvUgIxAiJI
=m+e8
-----END PGP SIGNATURE-----
Reply to: