From: Luis Felipe <luis.felipe.la@protonmail.com>
To: "gauthier@disroot.org" <gauthier@disroot.org>
Cc: Julien Lepiller <julien@lepiller.eu>,
Tissevert <tissevert+guix@marvid.fr>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: website: A little help running the website locally
Date: Thu, 27 May 2021 19:38:49 +0000 [thread overview]
Message-ID: <rkYNWreNpzfHLb7o4sNCWTabw1mHY9x7EV3N2WuQeJLH__VYB76iPr3BIDiIdNKSAtAUZxBVGbLvKFiGw5kZDn9J1dmaH5v85zXcsJEg7uY=@protonmail.com> (raw)
In-Reply-To: <8544c0d3baf4f8c5d020b0ed4ac30afd@disroot.org>
On Wednesday, May 26, 2021 1:46 PM, <gauthier@disroot.org> wrote:
> Just a heads up that due to this thread, I've been able to run the website locally too, that was one of my first realworld usage of guix, I'm slow on this journey, but I've started it :)
Great :)
> Regarding the website itself, I wanted to adjust the package page, so that it has a direct link to the package description from the github repository and I've not managed my guile foo (which is 0.00000001) enough to figure how to adjust the code already present in case of lint error.
>
> Maybe a current maintainer can wipe such change faster than waiting for me to advance my journey, I think it would benefit the website users to have direct link to the .scm from the package description page, or even having it pretty printed right on the page ideally.
I'm not sure I understand. I see that in the details page of a package there is a "Package source" field which links to the file and line where the package definition starts. See for example:
https://guix.gnu.org/en/packages/audacity-2.4.2/
Which links to audio.scm (https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/audio.scm#n683). Or is it that for some packages the link is not working?
In any case, I think it would be good to report any issue to the issue tracker (https://issues.guix.gnu.org/), if it isn't already reported.
next prev parent reply other threads:[~2021-05-27 19:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 13:53 website: A little help running the website locally Luis Felipe
2021-05-21 16:04 ` Tissevert
2021-05-21 16:38 ` Julien Lepiller
2021-05-21 16:48 ` Tissevert
2021-05-21 18:12 ` Luis Felipe
2021-05-21 18:17 ` Julien Lepiller
2021-05-21 18:33 ` Luis Felipe
2021-05-21 18:43 ` Luis Felipe
2021-05-21 18:55 ` Luis Felipe
2021-05-21 18:52 ` Julien Lepiller
2021-05-21 19:02 ` Luis Felipe
2021-05-21 19:24 ` Julien Lepiller
2021-05-21 19:28 ` Luis Felipe
2021-05-22 15:46 ` Julien Lepiller
2021-05-22 18:04 ` Luis Felipe
2021-05-26 13:46 ` gauthier
2021-05-27 19:38 ` Luis Felipe [this message]
2021-05-21 17:36 ` Luis Felipe
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='rkYNWreNpzfHLb7o4sNCWTabw1mHY9x7EV3N2WuQeJLH__VYB76iPr3BIDiIdNKSAtAUZxBVGbLvKFiGw5kZDn9J1dmaH5v85zXcsJEg7uY=@protonmail.com' \
--to=luis.felipe.la@protonmail.com \
--cc=gauthier@disroot.org \
--cc=guix-devel@gnu.org \
--cc=julien@lepiller.eu \
--cc=tissevert+guix@marvid.fr \
/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).