Re: Hyperlinks!

[Bengt Richter]

Hi Ludo,

On +2020-04-13 12:58:42 +0200, Ludovic Courtès wrote:
> Hello Guix!
> 
> Scheme code snippets in the on-line manual now have hyperlinks for all
> the symbols documented in the manual:
> 
>   
> https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-System.html
>   https://guix.gnu.org/manual/devel/en/html_node/Defining-Packages.html
> 
> Hyperlinks are such an amazing invention!
> 
> (If anyone knows how to get ‘a.syntax-symbol’ CSS different from just
> ‘a’, I’m all ears!)
> 
> This is happening in ‘doc/build.scm’ as a post-processing step on the
> makeinfo-generated HTML (along with the syntax-highlighting
> post-processing step).  It works well but there can be false positives
> because it matches on identifiers, without taking scope etc. into
> account—e.g., anytime “service” appears, it’ll link to the ‘service’
> procedure.
> 
> I’d like to extend it to include references to the Guile manual, so that
> one could click on, say, ‘append’, but there might be too many false
> positives at that point.  And then we would need DrRacket fanciness to
> be able to determine what an identifier really refers to…
> 
> Feedback welcome!
> 
> Ludo’.
> 

I think it important to have a very up-to-date version of docs
that can be downloaded like the single-page html doc alternatives
usually offered on gnu.org, for off-line use, and not have it too dependent
on secondary external links. (Or people might be tempted to
wget [options intentionally absent ;-]  to get more
to read off-line ;-).

Is https://guix.gnu.org/manual/en/guix.html in really good sync with
https://git.savannah.gnu.org/gitweb/?p=guix.git;a=blob;f=doc/guix.texi;h=891e2693f66672fc309b510ee2a5a4d5dd737db0;hb=8c04471f2403f05bcbea740e3722030e2b8311ec

(what's the easiest way to check? firefox page-info for
https://guix.gnu.org/manual/en/guix.html says
Modified: January 1, 1970, 1:00:01 AM GMT+1 ;-)

I like being able to do a git pull to get an updated version of a project
so I can trust it represents the latest official output from there.

But I like to read about a new project before I download the whole thing.
I prefer what I can believe is the latest official docs, not years-old web 
search results.
So I'll look for a git repo that I can browse for docs, preferring nicely 
hyperlinked ones.

I apppreciate not having to work to get tex or texi converted (as mostly happens
with package installs), but what if I (or a non-guix-user) just want to have 
the latest docs
without downloading the rest (or disturbing a current state), to read offline?
I think for that, pre-built single-page html should be available, please :)

If the latest is not easily available, people are likely to encounter guix on 
old
review pages or by following links from old stuff to old stuff, and may conclude
that guix is not even near ready for prime-time.

I think up-to-date wikipedia links are important, as people may go there out of 
interest
sparked elsewhere, to get up-to-date info on guix.
Is updating wikipedia part of guix documentation work-flow?

My 2¢ ;-)

-- 
Regards,
Bengt Richter

Re: Hyperlinks!

[pelzflorian (Florian Pelz)]

On Tue, Apr 14, 2020 at 09:09:24AM +0200, Bengt Richter wrote:
> I think it important to have a very up-to-date version of docs
> that can be downloaded like the single-page html doc alternatives
> usually offered on gnu.org, for off-line use, and not have it too dependent
> on secondary external links. (Or people might be tempted to
> wget [options intentionally absent ;-]  to get more
> to read off-line ;-).
> 

https://guix.gnu.org/manual-devel/

currently contains new stuff like the earlyoom service , while

https://guix.gnu.org/manual/

does not.  I do not know what the plan for these is though.

Regards,
Florian

Re: Porting status

[Ludovic Courtès]

Hi,

Vincent Legoll  skribis:

> To accompany the upcoming release I think
> it would be cool to add an architecture
> porting status page on the web site.
>
> The info is actually scattered between blog
> posts, mailing list, IRC logs, git branches...
>
> I'd like to have a clear status of :
> * what has been attempted
> * what is already working, WIP
> * where to find up to date informations
> * which branch to use
> * any potential performance problems
>
> For (32 / 64, le / be):
> - mips
> - arm
> - powerpc
> - i586, i686
>
> etc...

I think such a page is bound to become outdated, so I’m reluctant to
adding it.

Also, supporting an architecture has a significant cost (software
maintenance, hardware, CI, etc.).  Thus, we’ll probably only target
reasonably popular architectures, or architectures that are promising
from a free software perspective.

Thanks,
Ludo’.

Re: Hyperlinks!

[Ludovic Courtès]

Hi,

"pelzflorian (Florian Pelz)"  skribis:

> https://guix.gnu.org/manual-devel/

I’m surprised this URL works; should be
.

> currently contains new stuff like the earlyoom service , while
>
> https://guix.gnu.org/manual/
>
> does not.  I do not know what the plan for these is though.

/manual refers to the latest release.  This is so that the information
corresponds to the release that people download (in particular the
installation instructions).

Note that every time you run “guix pull”, you fetch an up-to-date copy
of the manual that can be browsed with ‘info’ or Emacs.  That’s still
the best way to ensure you’re reading a manual that corresponds to the
Guix you have.

Ludo’.

Re: Compressed ISO image got bigger

[Ludovic Courtès]

Hi!

Tobias Geerinckx-Rice  skribis:

>> It’d be ideal if we could have our cake and eat it too, but at any
>> rate
>> the ISO size improvement is welcome!
>
> Cake will be served once I (or someone else) get squashfs boot working
> reliably.  We'll no longer *have* an ‘uncompressed’ ISO at that point,
> we'll boot directly from XZ.

Nice!

> But that first requires support for (real) unencrypted /boot.

The ISO is not encrypted though.  Or you mean “uncompressed”?

Ludo’.

Re: Hyperlinks!

[Konrad Hinsen]

On 13/04/2020 13:13, Pierre Neidhardt wrote:

Ludovic Courtès  writes:


I’d like to extend it to include references to the Guile manual, so that
one could click on, say, ‘append’, but there might be too many false
positives at that point.  And then we would need DrRacket fanciness to
be able to determine what an identifier really refers to…

Perfect time for Rix, Guix in Racket!  Haha! :D


Easy. "Just" implement #lang guile in Racket ;-)


Cheers,

  Konrad.

Re: 1.1.0rc2 available for testing!

[Maxim Cournoyer]

Hello Mathieu,

Mathieu Othacehe  writes:

> Hey,
>
>> This bug is not about rc2, is it?  WDYT Mathieu?
>
> No, I think its a Guile-Parted bug, I forget about, that causes
> installer failures when the partition size is > 1 TiB. It has presumably
> always been around.
>
> I did a Guile-Parted 0.0.3 release and updated the package definition on
> master. However, I don't have the hardware to test the fix. So maybe we
> shouldn't block the 1.1.0 for this and wait for more feedback.

Apologies if I'm confusing things, but is this bug (about partition size
greater than 1 TiB the same as what I reported here:
https://gitlab.com/mothacehe/guile-parted/-/issues/1) ?

Maxim

Re: 1.1.0rc2 available for testing!

[Mathieu Othacehe]

Hello Maxim,

> Apologies if I'm confusing things, but is this bug (about partition size
> greater than 1 TiB the same as what I reported here:
> https://gitlab.com/mothacehe/guile-parted/-/issues/1) ?

I completely missed your report sorry about that. I need to activate
Gitlab notifications I guess :).

This is an unrelated issue that should be fixed with
eee637cab918b0f889edcdd7884970af6d8719cb. NVME disks were unsupported in
Parted 3.2, that I used when writing Guile-Parted.

Ludo, if we are on the way to a 1.1.0-rc3, maybe I could update
Guile-Parted to 0.0.4 and we could hope for installer support on NVME
disks and > 1 TiB disks. WDYT?

Thanks,

Mathieu

Fwd: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

[Gábor Boskovits]

To GSoC mentors:

I have received the following communication from the GNU coordinators:


-- Forwarded message -
Feladó: Jose E. Marchesi 
Date: 2020. ápr. 14., Ke 9:54
Subject: [gnu-soc] [IMPORTANT] Next steps for participating projects and
mentors
To: 



Hi people!

At this point students have sent proposals that can be reviewed in the
GSOC page [1].  By now you should have a good idea of how many proposals
you can/want to mentor.

So, we are asking you mentors to do the following this week, before
Saturday 18 April:

1) For each proposal you want to accept, please make sure there is at
   least one mentor in the "Want to mentor list".  Having a backup
   mentor is highly desirable.

2) Please send to this list the number of "essential slots" and "desired
   slots" for your GNU program.  As always we will be using these
   numbers to determine how many slots we will ask Google for, and to
   decide how to distribute the number of slots we get allocated.

Also note that we are still in time to register more mentors.
Thanks!

[1] https://summerofcode.withgoogle.com

Please make our internal deadline April 16th, 1600 UTC, so that I have time
to collect the responses, and to send out a draft to the ml, so anyone
missing can chime in.

Thanks

Best regards,
g_bor

Re: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

[Danny Milosavljevic]

Hi Gabor,

when I try to log in at https://summerofcode.withgoogle.com I get:

>403
>Ruh roh. Something went wrong here.
>Current Google account: danny.m...@gmail.com
>
>You don't have a GSoC account.
>[Get Started]

When I try to create an account using [Get Started], there are only the
choices "organization" and "student"--both of which I don't want.

Also, I'm pretty sure I am on the GSoC Mentors mailing list so I should
still have an account from last year, right?

(I'd like to mentor the PXE thing)


pgpPPbPvrI_8D.pgp
Description: OpenPGP digital signature

Re: [gnu-soc] [IMPORTANT] Next steps for participating projects and mentors

[Gábor Boskovits]

Hello Danny,

Danny Milosavljevic  ezt írta (időpont: 2020. ápr.
14., Ke 19:45):

> Hi Gabor,
>
> when I try to log in at https://summerofcode.withgoogle.com I get:
>
> >403
> >Ruh roh. Something went wrong here.
> >Current Google account: danny.m...@gmail.com
> >
> >You don't have a GSoC account.
> >[Get Started]
>
> When I try to create an account using [Get Started], there are only the
> choices "organization" and "student"--both of which I don't want.
>

That is correct, you can't use that ui.

>
> Also, I'm pretty sure I am on the GSoC Mentors mailing list so I should
> still have an account from last year, right?
>

Unfortunately that is not so. Registration is needed every year. You should
have received an invitation from the GNU org admins when you provided them
with you mentor information. That invitation should ensure that you account
gets registered and activated. If you did not receive your invitation, then
you should contact the GNU org admins on the gnu-soc mailing list, as only
they can invite you. If needed I can dig up the earlier communication, so
that you know what information they need.


> (I'd like to mentor the PXE thing)
>

Thanks, that is so nice.

Best regards,
g_bor

>

Re: Hyperlinks!

[Christopher Lemmer Webber]

This is very nice.  The rainbow parenthesis matching is really excellent
too.

Guix has managed to make Texinfo html export look really nice!  I admit
I expressed skepticism in this endeavour a number of years back and am
happy to be incorrect.


Ludovic Courtès writes:

> Hello Guix!
>
> Scheme code snippets in the on-line manual now have hyperlinks for all
> the symbols documented in the manual:
>
>   
> https://guix.gnu.org/manual/devel/en/html_node/Using-the-Configuration-System.html
>   https://guix.gnu.org/manual/devel/en/html_node/Defining-Packages.html
>
> Hyperlinks are such an amazing invention!
>
> (If anyone knows how to get ‘a.syntax-symbol’ CSS different from just
> ‘a’, I’m all ears!)
>
> This is happening in ‘doc/build.scm’ as a post-processing step on the
> makeinfo-generated HTML (along with the syntax-highlighting
> post-processing step).  It works well but there can be false positives
> because it matches on identifiers, without taking scope etc. into
> account—e.g., anytime “service” appears, it’ll link to the ‘service’
> procedure.
>
> I’d like to extend it to include references to the Guile manual, so that
> one could click on, say, ‘append’, but there might be too many false
> positives at that point.  And then we would need DrRacket fanciness to
> be able to determine what an identifier really refers to…
>
> Feedback welcome!
>
> Ludo’.

Re: sorting Rust crates [was Re: rav1e AV1 encoder]

[Martin Becze]

The problem should be fixed now. You can try it out about cloning `git 
clone https://gitlab.com/mjbecze/guix-package-sorter && cd 
guix-package-sorter` then do `./pre-install-env guix sort ` to 
sort the given file. Let me know if it works!


On 4/12/20 10:22 AM, Martin Becze wrote:
I apologize I didn't see this message until now. I will look into this 
today.


On 4/2/20 5:31 PM, Leo Famulari wrote:

On Fri, Feb 21, 2020 at 04:15:43AM -0500, Martin Becze wrote:

sort2.scm will sort a files exported packages alphanumerically.


I'm working on packaging rav1e for Guix again and so I'm using sort2.scm
on the big 'gnu/packages/crates-io.scm' module.

One problem I noticed with sort2.scm is that inherited packages need to
be after the package they inherit from, but this means they will not be
alphanumerically sorted.

For example, sort2.scm will put rust-bytes-0.3 before rust-bytes-0.4,
but then the build fails, because the former inherits from the latter
but can no longer find it.

Re: 1.1.0rc2 available for testing!

[Maxim Cournoyer]

Mathieu Othacehe  writes:

> Hello Maxim,
>
>> Apologies if I'm confusing things, but is this bug (about partition size
>> greater than 1 TiB the same as what I reported here:
>> https://gitlab.com/mothacehe/guile-parted/-/issues/1) ?
>
> I completely missed your report sorry about that. I need to activate
> Gitlab notifications I guess :).
>
> This is an unrelated issue that should be fixed with
> eee637cab918b0f889edcdd7884970af6d8719cb. NVME disks were unsupported in
> Parted 3.2, that I used when writing Guile-Parted.

Very nice!  Thanks for the follow-up and for your work on the installer.

Maxim