On 2023-03-21 21:04, Jack wrote:
I'd suggest looking at ebuilds created by g-cpan, which produces ebuilds for any module in CPAN.
I was looking at this early on but didn't think I would need it but it turned out that there was one more dependency I had missed. g-cpan worked very well, integrated itself automatically with Portage and put the generated ebuild in my localrepo. For now I just add g-cpan as a dependency to my ebuild with an elog message at the end with instructions how to install the missing module. I'll be looking for a way to trigger that automatically after the main program is emerged.
Regarding the location for the Perl modules created by znapzend, I ended up putting them in a separate folder for now until I can find some best practices on how to handle them. The ebuild works and I'm running tests on znapzend at the moment to see that I didn't miss more dependencies.
Thank you for your input and if anyone has info on best practices regarding Perl modules location and how to make your ebuild automatically put them in the current versioned vendor_perl folder, I'm all ears.
Morgan
