From: Christopher Baines <mail@cbaines.net>
To: Christopher Baines <mail@cbaines.net>
Cc: 39430-done@debbugs.gnu.org
Subject: bug#39430: Use CRAN’s canonical URL as home-page
Date: Tue, 15 Dec 2020 22:35:29 +0000 [thread overview]
Message-ID: <87lfdy3dfy.fsf@cbaines.net> (raw)
In-Reply-To: <87blex4zhk.fsf@cbaines.net>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Christopher Baines <mail@cbaines.net> writes:
> Lars-Dominik Braun <ldb@leibniz-psychology.org> writes:
>
>> I noticed for packages not specifying any URL the CRAN importer emits home-page
>> URLs like https://cran.r-project.org/web/packages/<package> (without trailing
>> slash). These are permanent redirects, thus the linter complains about them.
>> One option would be adding a trailing slash or use the canonical URL, as
>> provided by CRAN (on the bottom of the description page). The attached patch
>> does the latter.
>
> Hi,
>
> Sorry for the delay in following up on this.
>
> I gave this patch a try, testing using gProfileR as just a random
> package I picked.
>
> So, my take on this is that the canonical URLs still redirect, but using
> a 303 redirect, which the linter doesn't complain about. Given I see [1]
> on the page, I guess it makes sense to use these URLs.
>
> 1: Please use the canonical form https://CRAN.R-project.org/package=gProfileR to link to this page.
>
> I'll leave it a day or two for others to comment, as I'm not
> particularly familiar with CRAN, but I'm happy to merge this.
I've gone ahead and pushed this as
f14bb29defb36051039e977ba3791b542d90578a. I tweaked one of the variable
names.
Thanks again,
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 987 bytes --]
prev parent reply other threads:[~2020-12-15 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 7:49 [bug#39430] Use CRAN’s canonical URL as home-page Lars-Dominik Braun
2020-12-13 13:17 ` Christopher Baines
2020-12-15 22:35 ` Christopher Baines [this message]
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=87lfdy3dfy.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=39430-done@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.