Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2015-04-08

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

All times shown according to UTC.

Time Nick Message
00:24 ceridwen joined #marpa
04:47 ceridwen joined #marpa
06:16 ronsavage joined #marpa
10:23 lwa joined #marpa
10:25 pczarn joined #marpa
11:40 sirdancealot joined #marpa
15:10 jeffreykegler joined #marpa
20:24 sirdancealot joined #marpa
21:28 sirdancealot joined #marpa
21:50 koo5 joined #marpa
21:53 pczarn should I ask users to install libmarpa, or put marpa.c and the rest of generated code in my repository?
22:02 ronsavage joined #marpa
22:24 flaviu pczarn: libmarpa should be shipped as a dynamic library, there are still some LGPL components and that would be the easiest method of compliance.
22:35 koo7 joined #marpa
23:30 jeffreykegler joined #marpa
23:31 jeffreykegler pczarn: Right now llbmarpa has no release discipline, among other things.  It's intended for developer's like yourself, and *not* your users.
23:31 jeffreykegler You might want to look at how Marpa::R2 does it.
23:32 jeffreykegler Basically it
23:33 jeffreykegler 1.) Grabs a copy of the Libmarpa distribution and copies it into its own distribution.  Autoconf should be most stable, but there's also a cmake now.
23:34 jeffreykegler 2.) Logs the last 5 github commits of Libmarpa to a log file, and saves it as LOGDATA.  This will enable you, if worst comes to worst, match the distribution you copied with the repo.
23:35 jeffreykegler 3.)  Builds what it needs from the copy of the distribution, and installs accordingly.
23:36 jeffreykegler Summary: my advice is to *not* ask your users to install Libmarpa.

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