From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis Felipe =?UTF-8?Q?L=C3=B3pez?= Acevedo Subject: bug#22115: (no subject) Date: Sun, 18 Dec 2016 09:30:42 -0500 Message-ID: <1566bec1d2fd3ff566c73408c084b5b7@openmailbox.org> References: <878trdr1b9.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:49117) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cIcUR-0000cB-Gm for bug-guix@gnu.org; Sun, 18 Dec 2016 09:31:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cIcUQ-0004JA-Jp for bug-guix@gnu.org; Sun, 18 Dec 2016 09:31:03 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:58405) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cIcUQ-0004Ii-Gd for bug-guix@gnu.org; Sun, 18 Dec 2016 09:31:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1cIcUQ-0007Hd-3O for bug-guix@gnu.org; Sun, 18 Dec 2016 09:31:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <878trdr1b9.fsf@gnu.org> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: ludo@gnu.org Cc: 22115@debbugs.gnu.org On 2016-12-18 05:14, ludo@gnu.org wrote: > Luis Felipe López Acevedo skribis: > >> This bug is fixed in the website now: >> >> https://www.gnu.org/software/guix/packages/issues.html > > It really looks nicer this way, thank you! > > Initially the reason to include all the packages on this page (not just > those having issues) was that we could have links from, say, > /packages/c.html#coreutils to /packages/issues.html#coreutils. However > that never happened. I was going to ask why list all packages, but focused on the bug instead :) > Should we just list packages with actual issues? Or should we add > those > links? For now, I'd remove the packages without issues. This would help reduce the size of the page, which is almost 2 MiB (I use 1 MiB as a limit for desktop browsers). Soon™, I'd like to propose a package pages design where the package-list page indicates if a package has issues, and the package issues are listed in a package detail page (which does not exist yet). The current issues page would disappear. But I'll open a separate bug/proposal for this :) -- Luis Felipe López Acevedo http://sirgazil.bitbucket.org/