Packaging of libraries

[Dominique Dumont]

On Wednesday, 24 May 2017 19:17:37 CEST Daniel Dehennin wrote:
> I do not explore the opportunistic pre-compilation since a non root user
> will not be able to write under /usr/share/perl6/precomp/

Thanks for the analysis.

I'm still worried about the security implications of letting pre-compilation 
happens at run-time for a daemon. For instance, a web server based on Bailador 
would raise some security concerns because a bug in a web service could let an 
attacker an arbitrary pre-compiled file to "customize" the web server. But 
we're not there yet.

I've asked for feedback on debian-devel for the permanent tracker. I've heard 
some rumors that they are frowned upon. (I guess that a permanent transition 
tracker does not help untangle the other transitions...)

Otherwise, I've some code to handle pre-compilation at installation time, but 
it's not ready yet.

In the meantime, I think we could start packaging with simple Perl6 module, 
ship only source and let the pre-compilation happen in user's home dir. It may 
be better to add some explanation in README.debian and let user know what's 
goind on with ~/.perl6.

In the long run, I guess we'll end up with either a permanent tracker or pre-
compilation at installation time.

I've some bugs to clean up on Config::Model side. I'll resume work on rakudo 
once they are resolved.

All the best

-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org