unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Paul Wise <pabs3@bonedaddy.net>
Cc: 32261@debbugs.gnu.org
Subject: bug#32261: guix packages website: add mechanism to link to individual packages
Date: Tue, 24 Jul 2018 16:52:32 +0000	[thread overview]
Message-ID: <20180724165232.5vvn3byfwjrpw5jy@abyayala> (raw)
In-Reply-To: <eaf441134c8c9718dd3ab49f485de51512ad9adb.camel@bonedaddy.net>

Paul Wise transcribed 1.8K bytes:
> Hi all,
> 
> It used to be possible to link to individual Guix packages like this:
> 
> https://www.gnu.org/software/guix/packages/m.html#myrepos
> 
> Since the recent change to the packages website the packages pages are
> paginated and have no anchors, which means they will break as more
> packages are added and also I cannot link directly to a package,
> only to a location that contains lots of other packages too.
> 
> https://www.gnu.org/software/guix/packages/M/page/3/
> 
> Fixing this would be useful for the Repology support of GNU Guix,
> which currently cannot link to GNU Guix packages:
> 
> https://repology.org/repository/gnuguix
> https://repology.org/metapackage/myrepos/versions
> 
> -- 
> bye,
> pabs
> 
> https://bonedaddy.net/pabs3/

It is not just repology, but easy linking to details for external
parties/downstreams we need to point to somewhere.

I think there were some remaining ideas for the new websites,
where a package gets detail page on its own.


The pages are statically generated, 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.

  reply	other threads:[~2018-07-24 16:52 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 [this message]
2018-07-25  0:11   ` Paul Wise
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=20180724165232.5vvn3byfwjrpw5jy@abyayala \
    --to=ng0@n0.is \
    --cc=32261@debbugs.gnu.org \
    --cc=pabs3@bonedaddy.net \
    /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).