Call zef as a library

[JJ]

I'm not so sure this is possible right now, but it would be great if we could call it directly from the program without the need to get out to the shell and invoke it.

[niner]

The zef script is literally just:

#!/usr/bin/env perl6

use Zef::CLI;

The whole Zef codebase is very well structured. Alas, I don't think there are any guarantees about API stability. The question remains: why do you want to use zef in your program in the first place?

[FCO]

I have the same problem on 6pm. I've been working on this: FCO/zef@1c95922 to PR zef... but I still couldn't remove the no precompilation so I couldn't PR it yet...
Maybe something like that could be a solution for that...

[AlexDaniel]

Why is this in Sake repository?

[JJ]

@AlexDaniel so that we could have default support for install targets, for instance. But as @niner says, it's likely that we can do that directly from the Sakefile. I'll give it a try and propose an example to close this issue.

[JJ]

OK, now I remember: we can use Zef::CLI, but can we call it since all we have are MAIN functions

[AlexDaniel]

You sure you didn't mean to open it in https://github.com/ugexe/zef/issues ?

[JJ]

@AlexDaniel not really. I already did that. What I want to show (again) is why that would be useful.
If you look at tools such as Grunt or Gulp, they include plugins and ways of accessing native language facilities from within itself.

[niner]

But what exactly would Sake use the Zef libraries for?

[JJ]

Well, this is a wishlist... To have a default "install" target that could call zef as a functions instead of calling it from the shell. El mié., 30 oct. 2019 a las 12:41, niner (<[email protected]>) escribió:

…

But what exactly would Sake use the Zef libraries for? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#27>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAAD5BW2ESK4RB3B37CRGLQRFXFDANCNFSM4JGVLQ4A> .

-- JJ