Re: Who's who of the ecosystem?

[Vadim Belman]

For general language problems there is special repo on github where one can 
raise a matter: https://github.com/perl6/problem-solving 
. Note though it's not a 
bug-reporting resource, but more information about it's purpose can be found in 
repo's README.

Obviously, rakudo compiler issues goes into https://github.com/rakudo/rakudo/ 
. This would be the best place to open a 
ticket when one doesn't know where exactly the problem belongs to. Some tickets 
serve as a ground for new tickets in other repos, where they actually belong.

Now, as you specifically mention zef and the question has seemingly arisen as a 
part of R* discussion, it should be noted that zef is a personal project of 
Nick Logan and can be found at https://github.com/ugexe/zef 
.

Respectively, for any other module from the ecosystem it's repo could be 
located. I usually just google for it, but also 
https://github.com/perl6/ecosystem  could 
serve as a source of information.

Best regards,
Vadim Belman

> On Nov 6, 2019, at 9:48 AM, Parrot Raiser <1parr...@gmail.com> wrote:
> 
> Raku is the product of collaboration by many people. Some of these are
> well known, but there are many parts of the ecosystem whose mavens are
> anonymous or obscure. When a problem arises, it would be nice to be
> able to direct them to someone knowledgeable, rather than essentially
> yelling them in public and hoping someone responds to the noise.
> 
> Do we have any kind of resource, (web page or whatever), indicating
> who might be authoritative on a particular issue? Some names are
> fairly well-known, (and may wish they weren't), but topics like the
> internals of zef are hard to link to a person or group.
> 

Re: Rakudo Star 2019.07.1

[Patrick Spek via perl6-users]

Ah, that has been a mistake on my part, apologies. I can use a
more "correct" naming scheme in the future.

Are there any rules besides this one that release names should adhere
to? I'll write up a document about it so I have it documented, and
other people know what to expect as well.

On Wed, 6 Nov 2019 09:35:32 -0500
Parrot Raiser <1parr...@gmail.com> wrote:

> When I report a problem, I try to supply as complete a picture as
> possible, without imposing my filter on the data. So many times I've
> had a vital clue omitted by someone who "didn't think that X was
> important".
> 
> With so many parties involved, it's not surprising that errors reveal
> issues entirely outside your ken; those capable of fixing them may see
> the report and fix them.
> 
> > I'm not sure what you mean with "-n vs .n for sub-version ids". I  
> 
> The Rakudo* convention for normal releases was .MM, for
> experimental or supplemental releases was .MM-N, so my download
> script inserted "-" as the separator if given a third parameter, while
> you're using .MM.N I just changed the script, but again reported
> it in case someone else also uses a script.



-- 
With kind regards,

Patrick Spek


www:  https://www.tyil.nl/
mail: p.s...@tyil.nl
pgp:  1660 F6A2 DFA7 5347 322A  4DC0 7A6A C285 E2D9 8827

social: https://soc.fglt.nl/tyil
git:https://gitlab.com/tyil/


pgpLOD_0gjyk4.pgp
Description: OpenPGP digital signature

Who's who of the ecosystem?

[Parrot Raiser]

Raku is the product of collaboration by many people. Some of these are
well known, but there are many parts of the ecosystem whose mavens are
anonymous or obscure. When a problem arises, it would be nice to be
able to direct them to someone knowledgeable, rather than essentially
yelling them in public and hoping someone responds to the noise.

Do we have any kind of resource, (web page or whatever), indicating
who might be authoritative on a particular issue? Some names are
fairly well-known, (and may wish they weren't), but topics like the
internals of zef are hard to link to a person or group.

Re: Rakudo Star 2019.07.1

[Vadim Belman]

This is not really zef's "implementation detail". See rakudo sources in 
src/core.c/CompUnit and grep for 'sha1'.

Best regards,
Vadim Belman

> On Nov 6, 2019, at 9:04 AM, Patrick Spek via perl6-users 
>  wrote:
> 
> The problem is clearly with the Linenoise module, I'll have to look
> into that and see if it's something I can fix.
> 
> The path name you see is "an implementation detail" of Zef, I've been
> told before. I have no clue how it actually calculates them, and no
> idea where to find any documentation on that. That is something I
> cannot fix, and as far as I understand, there's no way this will be
> changed on the Zef side of things.
> 
> I'm not sure what you mean with "-n vs .n for sub-version ids". If this
> is causing issues or unclarities while trying to get Rakudo Star
> installed, I'll need some additional information in order to see if
> this is something I should fix or even can fix.
> 
> On Tue, 5 Nov 2019 17:15:26 -0500
> Parrot Raiser <1parr...@gmail.com > wrote:
> 
>> After a few difficulties caused by subtly different paths and version
>> identification (like -n vs .n for sub-version ids) the download and
>> installation appears to have worked, but trying the REPL produced the
>> following error message:
>> 
>> "I ran into a problem while trying to set up Linenoise: Failed to open
>> file 
>> /home/guru/rakudo/rakudo-star-2019.07.1/install/share/perl6/site/dist/91857A0CE92503F53D56DEBB6F633402878D0FF0:
>> No such file or directory
>> Continuing without tab completions or line editor"
>> 
>> I assume that horrendous filename is a SHA hash if some sort. To
>> whoever is involved with that part of the system, is there any chance
>> of generating shorter filenames to make understanding and
>> communication easier?
>> 
> 
> --
> With kind regards,
> 
> Patrick Spek
> 
> 
> www:  https://www.tyil.nl/ 
> mail: p.s...@tyil.nl 
> pgp:  1660 F6A2 DFA7 5347 322A  4DC0 7A6A C285 E2D9 8827
> 
> social: https://soc.fglt.nl/tyil 
> git:https://gitlab.com/tyil/ 


signature.asc
Description: Message signed with OpenPGP

Re: Rakudo Star 2019.07.1

[Parrot Raiser]

When I report a problem, I try to supply as complete a picture as
possible, without imposing my filter on the data. So many times I've
had a vital clue omitted by someone who "didn't think that X was
important".

With so many parties involved, it's not surprising that errors reveal
issues entirely outside your ken; those capable of fixing them may see
the report and fix them.

> I'm not sure what you mean with "-n vs .n for sub-version ids". I

The Rakudo* convention for normal releases was .MM, for
experimental or supplemental releases was .MM-N, so my download
script inserted "-" as the separator if given a third parameter, while
you're using .MM.N I just changed the script, but again reported
it in case someone else also uses a script.

Re: Rakudo Star 2019.07.1

[Patrick Spek via perl6-users]

The problem is clearly with the Linenoise module, I'll have to look
into that and see if it's something I can fix.

The path name you see is "an implementation detail" of Zef, I've been
told before. I have no clue how it actually calculates them, and no
idea where to find any documentation on that. That is something I
cannot fix, and as far as I understand, there's no way this will be
changed on the Zef side of things.

I'm not sure what you mean with "-n vs .n for sub-version ids". If this
is causing issues or unclarities while trying to get Rakudo Star
installed, I'll need some additional information in order to see if
this is something I should fix or even can fix.

On Tue, 5 Nov 2019 17:15:26 -0500
Parrot Raiser <1parr...@gmail.com> wrote:

> After a few difficulties caused by subtly different paths and version
> identification (like -n vs .n for sub-version ids) the download and
> installation appears to have worked, but trying the REPL produced the
> following error message:
> 
> "I ran into a problem while trying to set up Linenoise: Failed to open
> file 
> /home/guru/rakudo/rakudo-star-2019.07.1/install/share/perl6/site/dist/91857A0CE92503F53D56DEBB6F633402878D0FF0:
> No such file or directory
> Continuing without tab completions or line editor"
> 
> I assume that horrendous filename is a SHA hash if some sort. To
> whoever is involved with that part of the system, is there any chance
> of generating shorter filenames to make understanding and
> communication easier?
> 

-- 
With kind regards,

Patrick Spek


www:  https://www.tyil.nl/
mail: p.s...@tyil.nl
pgp:  1660 F6A2 DFA7 5347 322A  4DC0 7A6A C285 E2D9 8827

social: https://soc.fglt.nl/tyil
git:https://gitlab.com/tyil/


pgp8EIzg8yriD.pgp
Description: OpenPGP digital signature