Thanks, very much.
That talk inspired unhappiness in me, and I've even written my thoughts out,
but as all I've got is an unconstructive rant, I'm keeping it as an inspiration
until I can offer my own perl6 package manager that suits my prejudices.
A sample of one: if the problem is that perl6
The video I was talking about is now at
https://www.youtube.com/watch?v=uu8auCKCUN4
On 11 May 2016 at 15:38, Steve Mynott wrote:
> It's not a hack and the use of SHA files is basic to the requirements
> of how Perl 6 precomp works (totally different to how Perl 5 modules
> are used). Perl 6 is
nqp and moarvm are also split out in Fedora.
I have just succeeded in building panda (from panda's GIT) with a rakudo
star (lite) from Fedora.
I tried to use --prefix with bootstrap.pl. This built modules but did
not store them the right way (in hash). So useless at the end.
**perl bootstrap
I would also suggest stealing ideas from other packagers
Debian have Rakudo 2016.04 in sid
https://packages.debian.org/sid/rakudo
They have also split out nqp and moarvm packages.
S
On 11 May 2016 at 16:14, Steve Mynott wrote:
> Using an install outside the RPM/spec framework but also using
Using an install outside the RPM/spec framework but also using the
same config line
% perl Configure.pl --gen-moar --prefix /usr
[...]
Rakudo Star has been built and installed successfully.
Please make sure that the following directories are in PATH:
/usr/bin
/usr/share/perl6/site/bin
panda
On Wed, May 11, 2016 at 10:46 AM, Moritz Lenz wrote:
> On 05/11/2016 04:30 PM, Bennett Todd wrote:
>
>> Thanks for the explanation. Sounds like an unfortunate situation, rather
>> than letting the system admin choose modules within the limits of
>> filesystem namespace, it's using a separate dat
Thanks for the helpful note.
Perhaps I need to get to coding my own module installer. I appreciate that
"everything, everywhere, must support i18n" is noble, but I think it's pretty
ugly to encode filenames in the install tree on all systems, because there
exist systems that can't represent som
On 05/11/2016 04:30 PM, Bennett Todd wrote:
Thanks for the explanation. Sounds like an unfortunate situation, rather than
letting the system admin choose modules within the limits of filesystem
namespace, it's using a separate database, opaque to filesystem tools. I hope
this is just a tempor
It's not a hack and the use of SHA files is basic to the requirements
of how Perl 6 precomp works (totally different to how Perl 5 modules
are used). Perl 6 is using bytecode not the actual perl module. This
is also a moving target with work continuing.
nine gave a good talk on this at the recent
Thanks for the explanation. Sounds like an unfortunate situation, rather than
letting the system admin choose modules within the limits of filesystem
namespace, it's using a separate database, opaque to filesystem tools. I hope
this is just a temporary hack until a mature solution is hammered o
On Wed, May 11, 2016 at 10:21 AM, Bennett Todd
wrote:
> Zef seems to have left files containing the string Readline in
> share/perl6/site, plus .perl6/precomp. The filenames are hashes, perhaps
> from a git clone that zef used to pull Readline?
They're from rakudo's CompUnitRepo, which has to d
I never got panda to install, so I use zef.
The only module I've installed was Readline, to shut up the blind nagging
whenever I run perl6 for a repl.
Zef seems to have left files containing the string Readline in
share/perl6/site, plus .perl6/precomp. The filenames are hashes, perhaps from a
Sure better to have individual units as individual RPM.
I think Fedora is currently trying to succeed in rakudo-star full
installation before splitting. And on my hands the full installation
does not work if I uncomment the module-install (issues with paths
searched by panda bootstrap).
So, I
I think you're right, and the rpm packaging of perl5 is rather similar -- but
simpler, as there aren't the bifurcations into moarvm vs jvm, and panda vs zef.
But perl6 is young yet.
Happily, it's not too hard to package a single compiler, e.g. rakudo-moar. And
as long as you're comfy with rpmbu
It's probably useful experimenting with star itself and RPM but I
suspect bundling many modules inside one RPM isn't really the RPM way.
Probably there should be something like "rakudo-moar",
"rakudo-docs-noarch" RPM and a "rakudo-moar-panda" (or similar name)
RPM.
Handling rakudo-star versioned
15 matches
Mail list logo
