Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-toolchain, 2016-12-16

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
02:48 ilbot3 joined #perl6-toolchain
02:48 Topic for #perl6-toolchain is now Fire is step THREE! | https://github.com/perl6/toolchain-bikeshed | Channel logs: http://irclog.perlgeek.de/perl6-toolchain/today | useful prior art: https://metacpan.org/pod/CPAN::Meta::Spec
06:22 domidumont joined #perl6-toolchain
06:51 domidumont joined #perl6-toolchain
11:39 nine domidumont: I just pushed a couple of build system commits to nqp/rakudo which replaced the need for openSUSE specific patches by proper Configure.pl options. Your packages may need updates (simplifications), too.
11:40 nine I already added proper support for --with-moar=/usr/bin/moar to nqp and --with-nqp=/usr/bin/nqp a couple weeks ago. Makes building in a buildroot hassle free.
12:55 domidumont nine: thanks. I'll have to check if this fits Debian's needs. For reference here's the patch applied to rakudo build tools for Debian: https://anonscm.debian.org/cgit/pkg-rakudo/pkg-rakudo.git/tree/debian/patches/fix-lib-install-dir
13:09 nine Do you have any nqp patches?
13:18 nine I think your patch will still be needed. But maybe I get around to add a proper Configure.pl option for that for 2017.01.
13:21 domidumont nine: here are the nqp patches: https://anonscm.debian.org/cgit/pkg-rakudo/nqp.git/tree/debian/patches (they are less invasive than rakudo patches)
13:22 domidumont nine: and moar patch https://anonscm.debian.org/cgit/pkg-rakudo/pkg-moarvm.git/tree/debian/patches/fix-lib-install-dir
13:25 nine Ok, nothing should have changed there for you. We should however start talking about getting those upstream. Or rather finding upstream solutions that make the patches obsolete.
13:25 domidumont agreed
13:27 nine I do wonder though how you got by without patches similar to the openSUSE packages? Building as unprivileged user into a build directory instead of into prefix was practically impossible without those?
13:28 domidumont do you have a link to the opensuse patches ?
13:29 nine The sed commands in https://build.opensuse.org/package/view_file/home:niner9:branches:devel:languages:parrot/nqp/nqp.spec?expand=1
13:29 nine https://build.opensuse.org/package/view_file/home:niner9:branches:devel:languages:parrot/nqp/usenqplibdir.diff?expand=1
13:29 nine The sed commands in https://build.opensuse.org/package/view_file/home:niner9:branches:devel:languages:parrot/rakudo/rakudo.spec?expand=1
13:32 FROGGS joined #perl6-toolchain
13:33 domidumont I think opensuse doesn't care if arch dependant files and other are delivered in same dir. Debian does care. Hence the complex patch to make sure that arch independent files land in different directories compared to shared libs.
13:34 domidumont These are even delivered in different packages: rakudo and rakudo-libs
13:35 nine Oh it does care. Those packages may still be considered buggy in that way and I do see penalty points from the linter. It's just not enough points to have the packages rejected right away :)
13:35 domidumont uh.. right :-)
14:21 tadzik joined #perl6-toolchain
15:10 mst__ joined #perl6-toolchain
15:11 tadzik joined #perl6-toolchain
15:29 perlpilot joined #perl6-toolchain
16:54 domidumont joined #perl6-toolchain
16:57 domidumont joined #perl6-toolchain
17:01 domidumont joined #perl6-toolchain

| Channels | #perl6-toolchain index | Today | | Search | Google Search | Plain-Text | summary