From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out1.suse.de (smtp-out1.suse.de [IPv6:2001:67c:2178:6::1c]) by sourceware.org (Postfix) with ESMTPS id 3BBC23858D35 for ; Thu, 10 Nov 2022 09:39:17 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3BBC23858D35 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.cz Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=suse.cz Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 4731222183; Thu, 10 Nov 2022 09:39:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_rsa; t=1668073156; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O9Rlu7T6/syLcgwgXSNQjgCO2x8S9j0A6bYS4bYrX7o=; b=fIhol9AO2C1G82ynIXZ+IOVXBtjj/PD+/hNUEP+zvMztQYq7Fsy9oR2D75inpHUPAp5KLC Pg5P6ZRJ0L9ttRU9DdzcdrUKsc002JW2U7+rg6I1k+JXVdN2PuNANunaR8rAVeIuL915BS EXcR0x0gHBTtjN0en0PeR1A2iSjtzAQ= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.cz; s=susede2_ed25519; t=1668073156; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O9Rlu7T6/syLcgwgXSNQjgCO2x8S9j0A6bYS4bYrX7o=; b=x8We80rlMmO4DYLjVvSialmUYgAvu/Ux3D77g5zU1UlWuYbKkIniAExtvNA31cIzxOQRWg fToZW0hLkpQieGDg== Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id 344FE1346E; Thu, 10 Nov 2022 09:39:16 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id Iq29C8TGbGOHawAAMHmgww (envelope-from ); Thu, 10 Nov 2022 09:39:16 +0000 Message-ID: Date: Thu, 10 Nov 2022 10:39:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [DOCS] sphinx: use new Sphinx links Content-Language: en-US To: Gerald Pfeifer Cc: gcc-patches@gcc.gnu.org References: <482ae3dd-15f7-1e81-92e6-51a148e3bbc4@suse.cz> <2832f3b5-f815-3922-3681-edd55ca04dd5@suse.cz> <1656d2ca-f3b3-b46e-cf16-a6798e10deb1@suse.cz> <9c9b4969-dc72-a93b-335b-d72346bb437e@pfeifer.com> <8ae80e2a-9f49-4ebf-d7f0-815d32919573@suse.cz> <39fb5822-95aa-037a-5ac7-865e9096ff9f@pfeifer.com> From: =?UTF-8?Q?Martin_Li=c5=a1ka?= In-Reply-To: <39fb5822-95aa-037a-5ac7-865e9096ff9f@pfeifer.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,NICE_REPLY_A,SPF_HELO_NONE,SPF_SOFTFAIL,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 11/10/22 10:35, Gerald Pfeifer wrote: > On Thu, 10 Nov 2022, Martin Liška wrote: >>> What do you think of keeping the latest under this shorter and simpler >>> URL (too), though? >> Works for me. > : >>> I believe a symlink (in the file system) on gcc.gnu.org could pull that >>> off. >> Yep, please do so. > > Done. > > https://gcc.gnu.org/install/ is back with a new face. But it's not working properly due to some Content Security Policy: Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' http: https:". Either the 'unsafe-inline' keyword, a hash ('sha256-wAI2VKPX8IUBbq55XacEljWEKQc4Xc1nmwVsAjAplNU='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. gcc.gnu.org/:42 Refused to execute inline script because it violates the following Content Security Policy directive: "default-src 'self' http: https:". Either the 'unsafe-inline' keyword, a hash ('sha256-ySvT2PEZeueHGC1y2crNuNTfphBynFPP7i+U21fEgX0='), or a nonce ('nonce-...') is required to enable inline execution. Note also that 'script-src' was not explicitly set, so 'default-src' is used as a fallback. gcc.gnu.org/:47 Refused to apply inline style because it violates the following Content Security Policy directive: "default-src 'self' http: https:". Either the 'unsafe-inline' keyword, a hash ('sha256-biLFinpqYMtWHmXfkA1BPeCY0/fNt46SAZ+BBk5YUog='), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present. Note also that 'style-src' was not explicitly set, so 'default-src' is used as a fallback. gcc.gnu.org/:202 Refused to load the image 'data:image/svg+xml;charset=utf-8,' because it violates the following Content Security Policy directive: "default-src 'self' http: https:". Note that 'img-src' was not explicitly set, so 'default-src' is used as a fallback. Can you please take a look at it? > > Will you be reverting the link adjustments back from /onlinedocs/install/ > to plain /install/ ? Yes, I can do that. > > >>> Note how in style.mthml we have some special provisions for install/. >>> >>> Over the last years I have reduced those to a large extent. There is still >>> a little bit post-processing going on right now including setting our CSS >>> and our favicon. >> Well, the entire content of gcc.gnu.org/onlinedocs/install/ is *one* of >> our documentations and there should not be anything special about it. >> Does it make sense? > > Yes, things have evolved historically and there was a time we > needed/wanted to treat /install especially, for example to retain > the same (white) background color across. > > By now, if we are to make changes, we probably should rather make them > across all of /onlinedocs - favicon and our CSS being two such changes. > Not a critical priority, though, I guess. > > Gerald