From: Paul Wise <pabs3@bonedaddy.net>
To: Nils Gillmann <ng0@n0.is>
Cc: 32261@debbugs.gnu.org
Subject: bug#32261: guix packages website: add mechanism to link to individual packages
Date: Wed, 25 Jul 2018 08:11:52 +0800 [thread overview]
Message-ID: <2842ca9f0ad444ef3978fe4a3bf6172a1ce2f058.camel@bonedaddy.net> (raw)
In-Reply-To: <20180724165232.5vvn3byfwjrpw5jy@abyayala>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
On Tue, 2018-07-24 at 16:52 +0000, Nils Gillmann wrote:
> It is not just repology, but easy linking to details for external
> parties/downstreams we need to point to somewhere.
Indeed.
> I think there were some remaining ideas for the new websites,
> where a package gets detail page on its own.
That sounds good to me and is how a number of distros do it.
> The pages are statically generated
In that case, perhaps when a package is updated in the VCS, the static
generation tool could be triggered to update just that package.
> the old "useful" page format was taking a very long time to load,
> with each release and increase of package count we got k more
> seconds. Nothing I'd like to go back to.
Agreed, going back to the previous version would not be useful.
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-07-25 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 10:19 bug#32261: guix packages website: add mechanism to link to individual packages Paul Wise
2018-07-24 16:52 ` Nils Gillmann
2018-07-25 0:11 ` Paul Wise [this message]
2019-02-08 16:23 ` sirgazil
2019-02-10 20:50 ` sirgazil
2020-09-30 9:35 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2022-11-19 21:24 ` Luis Felipe via Bug reports for GNU Guix
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2842ca9f0ad444ef3978fe4a3bf6172a1ce2f058.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=32261@debbugs.gnu.org \
--cc=ng0@n0.is \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).