Perl 6 - the future is here, just unevenly distributed

IRC log for #native, 2017-01-13

| Channels | #native index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
01:12 willthechill plicease & jberger: RPerl must have gcc v4.7 or newer, I am now hitting CPAN tester failures in BSD w/ gcc v4.1 (ancient)... how to overcome?  must I truly build Alien::gcc?
01:14 plicease I would either drop your 4.7 requirement or not support such old BSDs
01:15 willthechill plicease: impossible to drop requirement, that's how RPerl works
01:15 willthechill I mean, I could delete all of RPerl...  :-P
01:16 plicease Then you can't support the old BSDs.
01:16 willthechill "can't" is what they said when I started working on RPerl
01:16 willthechill haha!  ;-)
01:16 willthechill is there any reason why Alien::gcc can not be built?
01:17 plicease seems a tad aggresive.
01:18 willthechill yes, RPerl makes extremely "aggressive" (extensive) use of the C++ compiler
01:18 willthechill remember, my current task is to get to 100% CPAN testers coverage
01:18 willthechill (a long-term goal, to be fair)
01:18 plicease you can certainly do what ever you want, but building gcc is an expensive process in terms of disk and cpu
01:18 plicease you may burn some good will with cpan testers if you do that.
01:19 willthechill ah yes, but with Alien::gcc it would NOT build gcc unless necessary?
01:21 plicease I am pretty sure I understood that calculation when I offered that advice.
01:23 willthechill okay
01:25 willthechill I was under the impression that, once a CPAN tester opts in to a test a particular distro, then they are "all in"?  usually RPerl takes up to 30 mins on a fast Linux box for building & testing, not counting any dependency tests...
01:25 willthechill I certainly don't want to burn any good will
01:25 plicease if you are interested, you can contact the cpantesters in question and gauge their opnion.
01:26 willthechill good point, I shall do so!
03:54 preaction as in uploading RPerl as a CPAN dist itself, and not as a Perl that sends in reports?
03:58 preaction also, there's the cpantesters-discuss mailing list, which might have more insight
05:03 willthechill preaction: sorry I don't understand what you mean by this?  "as in uploading RPerl as a CPAN dist itself, and not as a Perl that sends in reports?"
05:04 preaction are you uploading RPerl to CPAN as a Perl module? or should it be RPerl running tests against CPAN modules?
05:04 preaction RPerl is a Perl, not a Perl module, so it's kind of weird to use CPAN Testers to run RPerl's test suite
05:07 willthechill RPerl has always been on CPAN    https://metacpan.org/pod/RPerl
05:08 willthechill I expect it will take several more years before I can even begin to push for RPerl to be included in the Perl core
05:08 willthechill so until then, we pretend RPerl is "just another Perl module"
07:30 preaction joined #native
11:07 willthechill plicease: regarding Inline::gmake v0.17 and the need to add the parens as outlined in your CAVEATS section, does this affect Alien::astyle at all?  I don't ever call   use Alien::gmake
11:15 plicease willthechill: yeah, does not affect you.
11:15 willthechill okay great, thanks!  :-)
11:15 plicease pretty sure does not affect anyone.
11:16 willthechill ah okay, good to know
11:16 willthechill non-disruptive change
11:21 plicease if it does affect anyone they should get a big warning before it gets removed next year.
11:22 willthechill very good plan
11:30 willthechill I have abandoned the idea of Alien::gcc ... FOR NOW! (muahahahaha)
11:31 willthechill I've created compiler-checking code in my Makefile.PL and will bail instead of fail, no attempts to upgrade compiler
18:16 plicease sivoais: have you been able to get MSYS2 and strawberry to play nice together?
18:16 plicease it works if I have MSYS and make installed
18:16 plicease but if the mingw gcc is installed in MSYS stuff won't build
18:26 sivoais plicease: I tried a little, but I gave up after seeing just how much path manipulation was required especially with pkg-config. And I got everything working inside of MSYS2, so I don't have a pressing need for it.
18:27 sivoais The pain points are really just for building Perl modules that could use the MSYS2 libraries. I suppose that devs could take the native libraries from MSYS2 and copy them into Strawberry if the package layout is simple enough
18:29 plicease my preference would be to drop strawberry and work in msys2 also
18:30 plicease but strawberry seems to be used much more in the Perl community.
18:39 plicease I think I asked you that last time I was working on this.
18:39 plicease I appolagize for probably asking you again in six months :/
18:43 kaniini sivoais: what issues did you have with pkg-config?
18:50 sivoais kaniini: iirc, it was issues with using the the .pc files that were installed inside of MSYS2 with the pkg-config used by Strawberry Perl
18:51 kaniini ah
18:51 kaniini i cant do much about that.  the pkg-config would need to be cygwin-aware (or i suppose, MSYS2-aware) to handle the /mingw paths
18:53 sivoais we discussed this a little in this issue <https://github.com/PerlPkgConfig/perl-PkgConfig/issues/27>
20:54 willthechill joined #native

| Channels | #native index | Today | | Search | Google Search | Plain-Text | summary