bug#32261: guix packages website: add mechanism to link to individual packages

bug#32261: guix packages website: add mechanism to link to individual packages

[Paul Wise]

[-- Attachment #1: Type: text/plain, Size: 732 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/

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

bug#32261: guix packages website: add mechanism to link to individual packages

[Nils Gillmann]

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.

bug#32261: guix packages website: add mechanism to link to individual packages

[Paul Wise]

[-- 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 --]

bug#32261: guix packages website: add mechanism to link to individual packages

[sirgazil]

Hello Paul,

As Nils comments, the proposal in issue #25227 includes having a page 
per package in paths like: /packages/blender-X.Y.Z/. (Check 
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25227 for the details.)

If you think this issue is covered by that proposal, you could close 
this bug by sending an email to 32261-done@debbugs.gnu.org. You can use 
the same subject of this bug and summarize in the body why you are 
closing it.


:)


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/

bug#32261: guix packages website: add mechanism to link to individual packages

[sirgazil]

Hello Paul,

As Nils comments, the proposal in issue #25227 includes having a page 
per package in paths like: /packages/blender-X.Y.Z/. It is already 
possible to see a page per package at guix.info, but not at gnu.org
(check https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25227 for the details.)

If you think this issue is covered by that proposal, you could close 
this bug by sending an email to 32261-done@debbugs.gnu.org. You can use 
the same subject of this bug and summarize in the body why you are 
closing it.

:)


-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/

bug#32261: guix packages website: add mechanism to link to individual packages

[Tobias Geerinckx-Rice via Bug reports for GNU Guix]

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

Hi sirgazil,

You wrote:
> If you think this issue is covered by that proposal, you could 
> close
> this bug by sending an email to 32261-done@debbugs.gnu.org. You 
> can
> use the same subject of this bug and summarize in the body why 
> you are
> closing it.

I'm no Paul, but I don't think the above addresses this bug.  A 
package link that includes the version and breaks on the next 
upgrade is of limited use; in fact I can't think of any.

I'm leaving this bug open, but have closed the other one you 
mentioned in #guix.  Thanks!

Kind regards,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]

bug#32261: guix packages website: add mechanism to link to individual packages

[Luis Felipe via Bug reports for GNU Guix]

[-- Attachment #1.1: Type: text/plain, Size: 217 bytes --]

Hi,

It is now possible to link to packages like this:

https://packages.guix.gnu.org/packages/guile/

Which I think solves this issue, right?


---
Luis Felipe López Acevedo
https://luis-felipe.gitlab.io/

[-- Attachment #1.2: publickey - luis.felipe.la@protonmail.com - 0x12DE1598.asc --]
[-- Type: application/pgp-keys, Size: 1722 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 509 bytes --]